You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Preview crashes when i try to view images full screen???

I've only had my Macbook Pro for a few days, got the newest 15in model, and have already been doing some photo editing and such. Ive downloaded adobe photoshop elements 12, premeier elements 12, lightroom 5, kies for my phone, and firefox. When i want to view a photo in Preview in "full screen", like i should be able to, the whole app crashes, shuts all my open apps down, and returns me to my login screen. I'm able to open and view photos, amongst basic little corrections and such but no full screen. I then go and re-log on, and try to open the photo again full screen and the same thing happens yet again. It hasn't allowed me to view any images full screen yet, and i need this feature for presenting images in a class. I've tried restarting the whole computer etc, yet nothing works. Any ideas??

MacBook Pro with Retina display, OS X Mavericks (10.9)

Posted on Dec 10, 2013 8:21 PM

Reply
16 replies

Dec 10, 2013 9:32 PM in response to mountainbiker92

Launch the Console application in any of the following ways:


☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)


☞ In the Finder, select Go Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.


☞ Open LaunchPad. Click Utilities, then Console in the icon grid.


Step 1


Make sure the title of the Console window is All Messages. If it isn't, select All Messages from the SYSTEM LOG QUERIES menu on the left. If you don't see that menu, select

View Show Log List

from the menu bar.

Enter the name of the crashed application or process in the Filter text field. Select the messages from the time of the last crash, if any. Copy them to the Clipboard by pressing the key combination command-C. Paste into a reply to this message (command-V).

When posting a log extract, be selective. In most cases, a few dozen lines are more than enough.

Please do not indiscriminately dump thousands of lines from the log into this discussion.


Important: Some private information, such as your name, may appear in the log. Anonymize before posting.


Step 2


In the Console window, look under User Diagnostic Reports for crash reports related to the crashed process. The report name starts with the name of the process, and ends with ".crash". Select the most recent report and post the entire contents — again, the text, not a screenshot. In the interest of privacy, I suggest that, before posting, you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if it’s present (it may not be.) Please don’t post other kinds of diagnostic report — they're very long and not helpful.

Dec 10, 2013 11:27 PM in response to Linc Davis

The log (console) does not state that the application has crashed, and doesn't display any of those logs as stated above. I did before posting this question take a look at others who have had a similar issue, and tried to do that myself, to no avail. I should have mentioned that in the info bit above, however I wasn't sure that it applied to this issue.


Could it be that the image file is to big and Preview does not know what to do so it just goes nuts and crashes? Could it be that I have my computer passcode and it 'tricks' Preview into thinking that there is parental controls?

Dec 11, 2013 5:55 AM in response to mountainbiker92

If you have more than one user account, these instructions must be carried out as an administrator.

Still in the Console window, look under System Diagnostic Reports for crash reports related to the WindowServer process. The report name starts with "WindowServer" and ends with ".crash". Select the most recent one and post the entire contents — again, the text, not a screenshot. In the interest of privacy, I suggest that, before posting, you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if it’s present (it may not be.)

Dec 11, 2013 3:45 PM in response to Linc Davis

I only have the one account, but it is passcode protected. It is an administrator account.


these are the only three messages that i can make out to be related to "preview":


12/11/2013 3:36:58.989 PM Preview[533]: It does not make sense to draw an image when [NSGraphicsContext currentContext] is nil. This is a programming error. Break on void _NSWarnForDrawingImageWithNoCurrentContext() to debug. This will be logged only once. This may break in the future.


secondly:


12/11/2013 3:36:54.088 PM quicklookd[530]: Warning: Cache image returned by the server has size range covering all valid image sizes. Binding: VariantBinding [0x603] flags: 0x8 binding: FileInfoBinding [0x503] - extension: JPG, UTI: public.jpeg, fileType: ???? request size:32 scale: 1


and finally:


12/11/2013 3:36:54.087 PM com.apple.IconServicesAgent[235]: main Failed to composit image for binding VariantBinding [0x123] flags: 0x8 binding: FileInfoBinding [0x215] - extension: JPG, UTI: public.jpeg, fileType: ????.


Other than these messages there is nothing else that I can see that would relate to this issue. Granted I'm sure i don't know anything compared to many people out there, but it doesn't display that specific log that you are describing.

Dec 11, 2013 4:59 PM in response to mountainbiker92

Please read this whole message before doing anything.


This procedure is a test, not a solution. Don’t be disappointed when you find that nothing has changed after you complete it.


Step 1


The purpose of this step is to determine whether the problem is localized to your user account.


Enable guest logins* and log in as Guest. Don't use the Safari-only “Guest User” login created by “Find My Mac.”


While logged in as Guest, you won’t have access to any of your personal files or settings. Applications will behave as if you were running them for the first time. Don’t be alarmed by this; it’s normal. If you need any passwords or other personal data in order to complete the test, memorize, print, or write them down before you begin.


Test while logged in as Guest. Same problem?


After testing, log out of the guest account and, in your own account, disable it if you wish. Any files you created in the guest account will be deleted automatically when you log out of it.


*Note: If you’ve activated “Find My Mac” or FileVault, then you can’t enable the Guest account. The “Guest User” login created by “Find My Mac” is not the same. Create a new account in which to test, and delete it, including its home folder, after testing.


Step 2


The purpose of this step is to determine whether the problem is caused by third-party system modifications that load automatically at startup or login, by a peripheral device, by a font conflict, or by corruption of the file system or of certain system caches.


Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards. Boot insafe mode and log in to the account with the problem. Note: If FileVault is enabled on some models, or if a firmware password is set, or if the boot volume is a software RAID, you can’t do this. Ask for further instructions.


Safe mode is much slower to boot and run than normal, with limited graphics performance, and some things won’t work at all, including sound output and Wi-Fi on certain models. The next normal boot may also be somewhat slow.


The login screen appears even if you usually log in automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.


Test while in safe mode. Same problem?


After testing, reboot as usual (i.e., not in safe mode) and verify that you still have the problem. Post the results of steps 1 and 2.

Dec 12, 2013 8:19 PM in response to Linc Davis

OK, so here are the results of the two tests you gave me from above:


First test = no luck as a guest user:


12/12/2013 7:44:12.520 PM Preview[467]: persistentIdForFileURL: file:///Volumes/NO%20NAME/Project%204%20FINAL-****%20*****(3D%20Colour).jpg failed


12/12/2013 7:44:12.545 PM Preview[467]: It does not make sense to draw an image when [NSGraphicsContext currentContext] is nil. This is a programming error. Break on void _NSWarnForDrawingImageWithNoCurrentContext() to debug. This will be logged only once. This may break in the future.


Second test in safe mode DID work. Was slower when coming out of full screen mode however, but it did work.

From Second test:


12/12/2013 7:59:20.155 PM Preview[232]: It does not make sense to draw an image when [NSGraphicsContext currentContext] is nil. This is a programming error. Break on void _NSWarnForDrawingImageWithNoCurrentContext() to debug. This will be logged only once. This may break in the future.


12/12/2013 7:59:20.236 PM Preview[232]: CoreAnimation: failed to create OpenGL context


12/12/2013 8:00:05.751 PM Preview[232]: find_shared_window: WID 56


12/12/2013 8:00:05.751 PM Preview[232]: CGSClearWindowTags: Invalid window 0x38


***UPDATE*** The file that i used to test was about 13MB in size, which did not work in any test other than Safe Mode. The test image did work on an older 13" Macbook Pro, non retina display in full screen mode, so the file does work with other computers. I tested a smaller sized image as well around 2.5MB and Preview had no problem going into full screen mode with that image.


I have programs such as Adobe Photoshop Elements 12 and Premier Elements 12 installed on this computer as well as a few adobe utilities that were automatically downloaded as well with these programs. As well as firefox, and Kies for my samsung phone which has yet to be connected to this computer. I'm not worried about firefox or kies, but would like to not have to re-install Photoshop and Premier Elements again as they are serial code based downloads.

Dec 12, 2013 8:41 PM in response to mountainbiker92

Please read this whole message before doing anything.

This procedure is a diagnostic test. It changes nothing, and therefore will not, in itself, solve your problem.

Third-party system modifications are a common cause of usability problems. By a “system modification,” I mean software that affects the operation of other software — potentially for the worse. The procedure will help identify which such modifications you've installed, as well as certain other aspects of the configuration that may have a bearing on the problem. Don’t be alarmed by the apparent complexity of these instructions — they’re easy to carry out and won’t change anything on your Mac.


These steps are to be taken while booted in “normal” mode, not in safe mode, if possible. If you’re now running in safe mode, reboot as usual before continuing. If you can only boot in safe mode, you can still use this procedure, but not all of it will work. Be sure to mention that in your reply, if you haven't already done so.


Below are instructions to enter UNIX shell commands. The commands are safe and do nothing but produce human-readable text output, but they must be entered exactly as given in order to work. If you have doubts about the safety of the procedure suggested here, search this site for other discussions in which it’s been followed without any report of ill effects. I am not asking you to trust me. If you can't satisfy yourself that these instructions are safe, don't follow them.

The commands will line-wrap or scroll in your browser, but each one is really just a single long line, all of which must be selected. You can accomplish this easily by triple-clicking anywhere in the line. The whole line will highlight, and you can then copy it.

Note: If you have more than one user account, Step 2 must be taken as an administrator. Ordinarily that would be the user created automatically when you booted the system for the first time. Step 1 should be taken as the user who has the problem, if different. Most personal Macs have only one user, and in that case this paragraph doesn’t apply.

Launch the Terminal application in any of the following ways:


☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)


☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.


☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.


When you launch Terminal, a text window will open with a line already in it, ending either in a dollar sign (“$”) or a percent sign (“%”). If you get the percent sign, enter “sh” and press return. You should then get a new line ending in a dollar sign.


Step 1


Triple-click anywhere in the line of text below on this page to select it:

PB="/u*/*/Pl* -c Print"; { echo Loaded kernel extensions:; kextstat -kl | awk '!/com\.apple/{printf "%s %s\n", $6, $7}'; echo $'\nLoaded user agents:'; launchctl list | sed 1d | awk '!/0x|com\.apple|org\.(x|openbsd)|\.[0-9]+$/{print $3}'; echo $'\nInserted libraries:'; launchctl getenv DYLD_INSERT_LIBRARIES; echo $'\nUser cron tasks:'; crontab -l; echo $'\nGlobal launchd configuration:'; cat /e*/lau*; echo $'\nPer-user launchd configuration:'; cat .lau*; echo $'\nGlobal login items:'; $PB /L*/P*/loginwindow.plist | awk -F'= ' '/Path/{print $2}'; echo $'\nPer-user login items:'; $PB L*/P*/com.apple.loginitems.plist | awk -F'= ' '/Path/{print $2}'; echo $'\nSafari extensions:'; $PB L*/Saf*/*/E*.plist | awk -F'= ' '/Bundl/{print $2}' | sed 's/\..*$//;s/-[1-9]$//'; printf "\nRestricted user files: %s\n" $(find ~ $TMPDIR.. \( -flags +sappnd,schg,uappnd,uchg -o ! -user $UID -o ! -perm -600 \) | wc -l); echo $'\nExtrinsic loadable bundles:'; cd; find -L /S*/L*/E* {,/}L*/{Ad,Compon,Ex,In,Keyb,Mail/Bu,P*P,Qu,Scripti,Servi,Spo}* -type d -name Contents -prune | while read d; do /usr/libexec/PlistBuddy -c 'Print :CFBundleIdentifier' "$d/Info.plist" | egrep -qv "^com\.apple\.[^x]|Accusys|ArcMSR|ATTO|HDPro|HighPoint|driver\.stex|hp-fax|JMicron|print|SoftRAID" && echo ${d%/Contents}; done; echo $'\nUnsigned shared libraries:'; find /u*/{,*/}lib -type f -exec sh -c 'file -b $1 | grep -qw shared && ! codesign -v $1' {} {} \; -print; echo; ls -A {,/}L*/{La,Priv,Sta}* L*/Fonts; } 2> /dev/null | open -ef


Copy the selected text to the Clipboard by pressing the key combination command-C. Then click anywhere in the Terminal window and paste (command-V). I've tested these instructions only with the Safari web browser. If you use another browser, you may have to press the return key after pasting.

The command may take up to a few minutes to run, depending on how many files you have and the speed of the computer. A TextEdit window will open with the output. Post the contents of the TextEdit window (not the Terminal window) — the text, please, not a screenshot. You can then close the TextEdit window. The title of the window doesn't matter, and you don't need to post that. No typing is involved in this step.

Step 2


Remember that you must be logged in as an administrator for this step. Do as in Step 1 with this line:

{ echo "Loaded system agents:"; sudo launchctl list | sed 1d | awk '!/0x|com\.(apple|openssh|vix\.cron)|org\.(amav|apac|cups|isc|ntp|postf|x)/{print $3}'; echo $'\n'"Login hook:"; sudo defaults read com.apple.loginwindow LoginHook; echo $'\n'"Root cron tasks:"; sudo crontab -l; echo $'\n'"Log check:"; syslog -k Sender kernel -k Message CReq 'GPU |hfs: Ru|I/O e|find tok|n Cause: -|NVDA\(|pagin|timed? ?o' | tail | awk '/:/{$4=""; print}'; } 2> /dev/null | open -ef

This time you'll be prompted for your login password, which you do have to type. Nothing will be displayed when you type it. Type it carefully and then press return. You may get a one-time warning to be careful. Heed that warning, but don't post it. If you see a message that your username "is not in the sudoers file," then you're not logged in as an administrator.

You can then quit Terminal.

To prevent confusion, I'll repeat: When you type your password in the Terminal window, you won't see what you're typing.

Note: If you don’t have a login password, set one before taking Step 2. If that’s not possible, skip the step.

Important: If any personal information, such as your name or email address, appears in the output of these commands, anonymize it before posting. Usually that won't be necessary.

Remember, Steps 1 and 2 are all copy-and-paste — no typing, except your password. Also remember to post the output as text, not as a screenshot.

Please post the contents of the TextEdit window, not the Terminal window.

Dec 14, 2013 12:12 AM in response to Linc Davis

Results of the two steps as stated above, following the exact procedures as stated above, and this is done in the Normal Boot mode. I didn't have any issues with this at all, so here are the results per step:


Step 1:


Loaded kernel extensions:


Loaded user agents:


Inserted libraries:


User cron tasks:


Global launchd configuration:


Per-user launchd configuration:


Global login items:


Per-user login items:


Safari extensions:


Restricted user files: 36


Extrinsic loadable bundles:

/System/Library/Extensions/ssuddrv.kext

/Library/Internet Plug-Ins/Flash Player.plugin

/Library/PreferencePanes/Flash Player.prefPane

/Library/Spotlight/Microsoft Office.mdimporter


Unsigned shared libraries:


/Library/LaunchAgents:

com.adobe.AAM.Updater-1.0.plist


/Library/LaunchDaemons:

com.adobe.fpsaud.plist


/Library/PrivilegedHelperTools:


/Library/StartupItems:


Library/Fonts:


Library/LaunchAgents:

com.adobe.AAM.Updater-1.0.plist



Step 2:


Loaded system agents:

com.adobe.fpsaud


Login hook:


Root cron tasks:


Log check:

Dec 8 19:16:45 kernel[0] <Debug>: Previous Shutdown Cause: -128

Dec 9 18:42:59 kernel[0] <Debug>: PM notification timeout (pid 1273, Messages)

Dec 11 08:16:35 kernel[0] <Debug>: Sound assertion - Command/Response TIMED OUT and ( kRequestStateMatch == fCodecRequest->state = 2 ), fCodecRequest->command->codec: 0xffffff8025f32e00, fCodecRequest->command->verb: 0x1F0500, fPoweredDown: 1, fAppleGraphicsControllerPoweredOn: 0

Dec 13 12:41:14 kernel[0] <Debug>: Sound assertion - Command/Response TIMED OUT and ( kRequestStateMatch == fCodecRequest->state = 2 ), fCodecRequest->command->codec: 0xffffff8029907800, fCodecRequest->command->verb: 0x1F0500, fPoweredDown: 1, fAppleGraphicsControllerPoweredOn: 0

Dec 13 12:41:20 kernel[0] <Debug>: Sound assertion - Command/Response TIMED OUT and ( kRequestStateMatch == fCodecRequest->state = 2 ), fCodecRequest->command->codec: 0xffffff8029907800, fCodecRequest->command->verb: 0x17FF00, fPoweredDown: 1, fAppleGraphicsControllerPoweredOn: 0

Dec 13 12:41:21 kernel[0] <Debug>: Sound assertion - Command/Response TIMED OUT and ( kRequestStateMatch == fCodecRequest->state = 2 ), fCodecRequest->command->codec: 0xffffff8029907800, fCodecRequest->command->verb: 0x1F0500, fPoweredDown: 1, fAppleGraphicsControllerPoweredOn: 0

Dec 14, 2013 6:33 AM in response to mountainbiker92

Please read this whole message carefully, especially the warnings, before doing anything.

1. I can only guess which of the modifications you've made to your system is causing the problem. The changes suggested here should be considered provisional; they may not help, or they may remove functionality that you find useful. If a third-party system modification that you want to keep is at fault, refer to its developer for support.

2. WARNING: Back up all data now if you haven’t already done so. Before proceeding, you must be sure you can restore your system to its present state, even if it becomes unbootable. If you’re not sure you can do that, STOP — DON’T CHANGE ANYTHING.

If you don't like the results of the procedure suggested below, restore from your backup.

I will not be responsible for the consequences, and I will not be able to help, if you ignore this warning.

3. You should either remove or update the following system modification(s), if an update is available from the developer:

[Not applicable]

and definitely remove at least the following:

Samsung Kies

4. Whatever you remove must be removed completely, and (unless otherwise specified in this message) the only way to do that is to use the uninstallation tool, if any, provided by the third-party developers, or to follow their instructions. If the software has been incompletely removed, you may have to re-download or even reinstall it in order to finish the job. I can't be more specific, because I don't install such things myself. Please do your own research.

Here are some general guidelines to get you started. Suppose you want to remove something called “BrickMyMac” (a hypothetical example.) First, consult the product's Help menu, if there is one, for instructions. Finding none there, look on the developer's website, say www.brickmymac.com. (That may not be the actual name of the site; if necessary, search the web for the product name.) If you don’t find anything on the website or in your search, contact the developer. While you're waiting for a response, download BrickMyMac.dmg and open it. There may be an application in there such as “Uninstall BrickMyMac.” If not, open “BrickMyMac.pkg” and look for an Uninstall button.

Again, please don't ask me to do this research for you. You can do it better than I can, because I don't use the product and I may not even know what it is.

You will generally have to reboot after uninstalling a system modification. Until you do that, the uninstallation may have no effect, or unpredictable effects.

5. If you can’t remove software in any other way, you’ll have to erase and install OS X. Never install any third-party software unless you're sure you know how to uninstall it; otherwise you may create problems that are very hard to solve.

WARNING: Trying to remove complex system modifications by hunting for files by name often will not work and may make the problem worse. The same goes for "utilities" such as "AppCleaner" and the like that purport to remove software.

6. I recommend that you never reinstall the modifications marked with a dagger (†) above, if any. If your problem is resolved after uninstalling all the above modifications and rebooting, but you still want to use some of those not marked with a dagger, you can experiment with putting them back, one at a time, testing carefully after each step. Keep in mind that system modifications may be incompatible with each other or with future OS X updates, so it may not be clear which one is at fault.

7. If you still have problems after making the suggested changes and rebooting, post again. Remember: if you don’t like the results of this procedure, you can undo it by restoring from the last backup you made before you started.

Dec 15, 2013 8:32 PM in response to Linc Davis

So far I have removed from my computer the following programs:

Samsung Kies

Mozilla Firefox

and a few Adobe add ons that were not necessary.


Each time I have removed a program I have restarted my computer manually, as it did not prompt me to automatically restart, each time I removed a different program, the Preview app would still function as it has previously.


I have also attempted to save the image file as a .tif file instead of a .jpeg file and still no luck. Possibly the images I'm creating are 64-bit and preview only supports 32-bit? Which would seem odd, as this computer is the highest end Macbook to date, and should have no issues with anything at all.


The end result of my tests so far have come up with nothing. Where to from here?

Dec 15, 2013 11:22 PM in response to Linc Davis

Only some at this point, it seems file size is a key role, however that's the only thing that is apparent to me. However background things such as RBG colour scheme, or whether or not the image is 64 or 32 bit could also play a factor, however I can't say for sure. Larger size files, (test image size was 13 MB) will not go full screen, while smaller image sizes, >2MB will. I cannot test more images at this point because my computer is so new, maybe a week old, and I'm not wanting to transfer any of my images, audio or other files from my previous computer without first resolving this issue. As well as not wanting to make everything that much more confusing by adding in thousands more files to sift through to get to the problem.


I will look to see what I can find elswhere.


This forum mentions something about a specific file named: com.apple.Preview.plist with a path of:


HD/Users/YourUserName/Library/Preferences/com.apple.Preview.plist


However when I went to look for this file, it does not exist on my computer in that path. Is this a file my computer and OS need to properly run this app?


http://www.mac-forums.com/forums/os-x-operating-system/229351-preview-keeps-cras hing.html


***UPDATE*** I sure hope this helps out, because it's been the biggest breakthrough I've had so far.

When opening the Preview app from: HD/Applications/Preview.app(open package contents here)/Contents/MacOS/Preview (in this case it says it's a Unix Executable File) I HAVE been able to open my larger images that previously would not open by doing this. HOWEVER, they open momentarily, and EXTREMELY slowly for what this computer should be capable of, and when you press ESC to exit full screen mode the system hangs itself and I am once again back to the login screen.


Full excerpt from terminal as launched from the process as stated above (I will edit out names and identifying items with this symbol * )


Last login: Sun Dec 15 22:51:32 on ttys001

*****-MacBook-Pro:~ *********$ /Applications/Preview.app/Contents/MacOS/Preview ; exit;

2013-12-15 22:54:05.672 Preview[719:507] It does not make sense to draw an image when [NSGraphicsContext currentContext] is nil. This is a programming error. Break on void _NSWarnForDrawingImageWithNoCurrentContext() to debug. This will be logged only once. This may break in the future.

[Restored]

*****-MacBook-Pro:~ *********$




The above does not state when or what Preview.app executed to go full screen, I'm not sure if it usually does, however this covers the whole time that I was able to open Preview.app until it crashed or whatever it did to make my computer return to the login screen.





Some forums are saying to create a totally new user account, not a guest account, and attempt it that way before continuing, granted the issues with preview are not the same, generally for people it seems to just crash after about 10 mins, however this could possibly work in my situation as well. From the second user account I would then cross match the files in the /username/Library/Preferences folders, identify the ones that match in the second user account to the main user account and copy all the matching files from the main user account to the desktop and then back into the preferences folder of the main user account, and then restart. This sounds extremely complicated and time consuming, I will post the link to that forum and see what you think.


Here: https://discussions.apple.com/thread/2732658?start=15&tstart=0

Dec 16, 2013 7:18 AM in response to mountainbiker92

Some forums are saying to create a totally new user account, not a guest account


You tested in the Guest account and the results were the same, according to an earlier response. If that response was accurate -- and I have to assume that it was -- it rules out anything in your home folder as the cause.


I've seen a few other reports similar to yours. I believe the current version of Preview has a crashing bug triggered by some images exported from Adobe applications. So far I haven't come across a publicly-available file that I can test. That's why I'm asking whether you know of one.

Dec 16, 2013 8:05 AM in response to mountainbiker92

Have you tried the basic steps first? Finder Menu <Go<Utilitilies<Disk Utilities, then select Macintosh HD- to the right First Aide should already be selected and greyed out, then below the white space window, select "Repair Disk Permissions", once that is finished. Shutdown the computer properly and reset the PRAM. To do this you must hold down, the following keys at the same time: Option, Command, R, and P. Hold these keys down before and while powering on the computer, please make sure you release the power button once you power the computer on. Don't release the four keys above until after you have heard the second chime. Then, wait for you logon screen, unless you bypass a login screen. Open preview and see if that works.

Preview crashes when i try to view images full screen???

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.