Mac crashes while safari is in full screen

Hi!


It is happened a number of times now that I am using safari in full screen and the whole system freezes. The cursor does not respond and the only way to interact with the machine is to long press the power button the device. Even when closing the laptop, the Apple logo is switched on.


I am using the Macbook Pro early 2015 model, 2.7 GHz Intel core i5, 128 gb and running OS X el capitan latest version available: 10.11.4 and also running the latest version of Safari.


Thanks!

MacBook Pro with Retina display, OS X El Capitan (10.11.4), 128 gb

Posted on Apr 15, 2016 9:42 AM

Reply
5 replies

Apr 15, 2016 12:43 PM in response to Owzamsa

You may have a Safari extension or third party plug-in installed that's causing a conflict in full screen mode. It's easy to troubleshoot.


From the Safari menu bar click Safari > Preferences then select the Extensions tab. If there are any extensions installed, uninstall one at a time then quit and relaunch Safari to test.



If it's not an extensions issue, try troubleshooting third party plug-ins.


Back to Safari > Preferences. This time select the Security tab. Deselect: Allow plug-ins. Quit and relaunch Safari to test.


If that made a difference, instructions for troubleshooting plugins here.

Apr 15, 2016 3:00 PM in response to Owzamsa

These instructions must be carried out as an administrator. If you have only one user account, you are the administrator.

Please launch the Console application in any one 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 and start typing the name.

Step 1

For this step, the title of the Console window should be All Messages. If it isn't, select

SYSTEM LOG QUERIES All Messages

from the log list on the left. If you don't see that list, select

View Show Log List

from the menu bar at the top of the screen.

In the top right corner of the Console window, there's a search box labeled Filter. Enter "BOOT_TIME" (without the quotes.)

Each message in the log begins with the date and time when it was entered. Select the BOOT_TIME log message that corresponds to the last boot time when you had the problem. Now clear the search box to reveal all messages. Select the ones logged before the boot, during the time something abnormal was happening. Copy them to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.

For example, if the system was unresponsive or was failing to shut down for three minutes before you forced a restart, post the messages timestamped within three minutes before the boot time, not after. Please include the BOOT_TIME message at the end of the log extract—not at the beginning.

If there are long runs of repeated messages, please post only one example of each. Don’t post many repetitions of the same message.

When posting a log extract, be selective. A few dozen lines are almost always more than enough.

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

Please don't indiscriminately dump thousands of lines from the log into this discussion.

Please don't post screenshots of log messages—post the text.

Step 2

In the Console window, select

DIAGNOSTIC AND USAGE INFORMATION System Diagnostic Reports

(not Diagnostic and Usage Messages) from the log list on the left. If you don't see that list, select

View Show Log List

from the menu bar.

There is a disclosure triangle to the left of the list item. If the triangle is pointing to the right, click it so that it points down. You'll see a list of reports. A crash report has a name that begins with the name of the crashed process and ends in ".crash". A panic report has a name that begins with "Kernel" and ends in ".panic". A shutdown stall report has a name that ends in ".shutdownstall". Select the most recent of each, if any. The contents of the report will appear on the right. Use copy and paste to post the entire contents—the text, not a screenshot. It's possible that none of these reports exists.

I know the report is long, maybe several hundred lines. Please post all of it anyway.

If you don't see any reports listed, but you know there was a crash or panic, you may have chosen Diagnostic and Usage Messages from the log list. Choose DIAGNOSTIC AND USAGE INFORMATION instead.

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 rarely helpful.

When you post the log extract or the crash report, you might see an error message on the web page: "You have included content in your post that is not permitted," or "The message contains invalid characters." That's a bug in the forum software. Please post the text on Pastebin, then post a link here to the page you created.

If you have an account on Pastebin, please don't select Private from the Paste Exposure menu on the page, because then no one but you will be able to see it.

Apr 26, 2016 7:40 PM in response to Owzamsa

Owzamsa --


Questions for you:

1. When you're in Safari NOT in fullscreen -- does it still crash?

2. Do you get the option to report to Apple? If so, click yes, and copy the report and paste it in your next post here.

(It is perfectly OK to post that report here).

3. What version of Flash are you running? Check System Preferences > Other.

Apr 27, 2016 7:00 AM in response to Owzamsa

Try a restart.


Do a backup, using either Time Machine or a cloning program, to ensure files/data can be recovered. Two backups are better than one.


Try setting up another admin user account to see if the same problem continues. If Back-to-My Mac is selected in System Preferences, the Guest account will not work. The intent is to see if it is specific to one account or a system wide problem. This account can be deleted later.


Isolating an issue by using another user account


If the problem is still there, try booting into the Safe Mode using your normal account. Disconnect all peripherals except those needed for the test. Shut down the computer and then power it back up after waiting 10 seconds. Immediately after hearing the startup chime, hold down the shift key and continue to hold it until the gray Apple icon and a progress bar appear. The boot up is significantly slower than normal. This will reset some caches, forces a directory check, and disables all startup and login items, among other things. When you reboot normally, the initial reboot may be slower than normal. If the system operates normally, there may be 3rd party applications which are causing a problem. Try deleting/disabling the third party applications after a restart by using the application un-installer. For each disable/delete, you will need to restart if you don't do them all at once.





Safe Mode - About El Capitan


Safe Mode Startup – El Capitan.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Mac crashes while safari is in full screen

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