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

Safari slow to load url's and .css file and extensions cause other issues

I am currently running Mountain Lion and Safari 6 on 27 iMac (mid 2010) ALL .css files (style sheets) and extensions that allow automated zooming of the browser window are causing problems with both 'jumping pages' and the ability to use iCloud/iwork tabs (numbers, pages, keynote) with these files and extension on. So if you have these installed you may find that disabling the extension or removing the style sheet (.css) will help the situation. ATS was able to reconstruct the same issue.


However I cannot find a way to make the Safari 6 browser wake up and go. It is running about half the speed of its predecessor in Lion. I have completely reinstalled ML, firmware updates for timecapsule, trashed preferences, reset Safari, added DNS, turned off all extensions to no avail!


With all the other postings I am seeing it appears that this was put out there under very little testing. I really hope that iso 6 is not released with this many bugs. Lets go Apple!


Any other suggestions would be appreciated.

OS X Mountain Lion, 27 iMac , iPad 3, iPhone 4s

Posted on Aug 4, 2012 6:27 PM

Reply
23 replies

Aug 5, 2012 12:07 PM in response to icebugs

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. For instructions, launch the System Preferences application, select Help from the menu bar, and enter “Set up a guest account” (without the quotes) in the search box. 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(s)?


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 in OS X 10.7 or later, 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.


Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards. Boot in safe mode* and log in to the account with the problem. The instructions provided by Apple are as follows:


  1. Be sure your Mac is shut down.
  2. Press the power button.
  3. Immediately after you hear the startup tone, hold the Shift key. The Shift key should be held as soon as possible after the startup tone, but not before the tone.
  4. Release the Shift key when you see the gray Apple icon and the progress indicator (looks like a spinning gear).


Safe mode is much slower to boot and run than normal, and some things won’t work at all, including wireless networking on certain Macs.


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.


*Note: If FileVault is enabled under OS X 10.7 or later, or if a firmware password is set, you can’t boot in safe mode.


Test while in safe mode. Same problem(s)?


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.

Aug 5, 2012 5:03 PM in response to Linc Davis

Hi Linc,

Thanks for the response. Step one returned the results Safari worked a little bit faster but not as fast as it had under Lion.

In the process of running step two I ran into additional problems. Specifically Time Machine problems, crashes finder, and slower than normal Safari browser. Finder windows open and close and open to close and flashing flashing flashing.

At that point I reinstalled Mountain lion. Call technical support at Apple. I am currently doing a clean install of mountain lion on my iMac. According to Apple technical support it is a systemwide problem and this will resolve the issue. I will repost once the install is complete and I have had a chance to test all aspects.

Mike

Aug 6, 2012 5:59 PM in response to Linc Davis

Linc, Well....that did not fix the issue with slow Safari and now the FInder issues are continuing. These Finder issues include multiple finder window crashes when selecting the home folder, finder switches to open applications when selecting the home folder, Sometimes the Finder window crashes when opening from the file menu, sometimes the HD and sometimes from the dock. Sometimes it works and then if you relaunch the Finder or restart the computer it starts all over again. This continues in Safe Mode under main user account but does NOT replicate under a 'Test User Account' ATS sent me a data capture app for Engineering to evaluate and I should find out more in a few days.


ATS said I can create a new user and manually transfer my documents over and then the issue would probably stop. What do you think of that? And what if any precautions can you think of?

Aug 6, 2012 6:11 PM in response to Linc Davis

I am just reaching out here for imput. I understood your post perfectly and knew it was an information request. Safari was slow in Step 1 but not as slow as under the main user account (i.e loading discussion.apple.com takes about 90 seconds) I ran into other issues with Finder before I could proceed with Step 2. Thats when ATS had me do a clean install. We are getting the same results in Safe Mode.


My comment about that not fixing the issue was in referance to the Clean install.

Aug 6, 2012 6:21 PM in response to Linc Davis

I am just reaching out here for imput. I understood your post perfectly and knew it was an information request. Safari was slow in Step 1 but not as slow as under the main user account (i.e loading discussion.apple.com takes about 90 seconds) I ran into other issues with Finder before I could proceed with Step 2. Thats when ATS had me do a clean install. We are getting the same results in Safe Mode.


My comment about that not fixing the issue was in referance to the Clean install.

Aug 6, 2012 6:57 PM in response to icebugs

Problems such as yours are sometimes caused by files that should belong to you but are locked or have a wrong owner. This procedure will check for such files. It makes no changes and therefore will not, in itself, solve your problem.

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 page that opens.

Triple-click anywhere in the line below to select it, then drag or copy it — do not type — into the Terminal window:

find . $TMPDIR.. \( -flags +sappnd,schg,uappnd,uchg -o ! -user $UID \) -ls

Press return. The command may take a noticeable amount of time to run. Wait for a new line ending in a dollar sign (“$”) to appear.

Post any lines of output that appear below what you entered — the text, please, not a screenshot.

If any personal information appears in the output, edit before posting, but don’t remove the context.

Aug 6, 2012 7:16 PM in response to icebugs

No, please don't.


The procedure below will reset the permissions of a home folder in OS X 10.7.4 or later. If you're running an earlier version of 10.7, update to the latest version first. This procedure should not be used in OS X versions older than 10.7.4.

Back up all data before you begin.

Step 1

Click the Finder icon in the Dock. A Finder window will open.

Step 2

Press the following key combinations, in the order given:


Command-3
Shift-command-H
Command-I

The Info window of your home folder will open.

Step 3

Click the lock icon in the lower right corner and authenticate with the name and login password of an administrator on the system. If you have only one user account, you are the administrator.

Step 4

In the Sharing & Permissions section of the window, verify that you have "Read & Write" privileges. If not, use the "+" and "-" buttons in the lower left corner to make the necessary changes.

Step 5

By default, the groups "staff" and "everyone" have "Read Only" privileges. With those settings, the files at the top level of your home folder will be readable by other local users. You can change the privileges to "No Access" if you wish, but then your Public and Drop Box folders will be inaccessible to others, and Personal Web Sharing won't work. Most likely, you don't need to change these settings.

Step 6

If there are entries in the Sharing & Permissions list for users or groups besides "me," "staff," and "everyone," delete them.

Step 7

Click the gear icon at the bottom of the Info window and select Apply to enclosed items... from the drop-down menu. Confirm. The operation may take several minutes to complete. When it does, close the Info window.

Aug 6, 2012 7:53 PM in response to Linc Davis

Linc,

I followed the steps for permissions as described. Finder still crashing. Ran terminal again and it showed a similarly large return pointing to one folder. I backed up the folder (seperate drive) and deleted it. Restarted and the Finder still crashng. Ran terminal again and the return is empty. Safari is still slow especially when going to discussions. Thoughts?

Aug 6, 2012 8:21 PM in response to icebugs

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 page that opens.


Step 1


Enter the name of the crashed application or process in the Filter text field. Post the messages from the time of the last crash, if any — the text, please, not a screenshot.


Important: Some private information, such as your name, may appear in the log. Edit it out by search-and-replace in a text editor before posting.


Step 2


Still in the Console window, look under User Diagnostic Reports for crash reports related to the process. The report name starts with the name of the crashed process, and ends with ".crash". Select the most recent report and post the 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 shutdownStall, spin, or hang logs — they're very long and not helpful.

Safari slow to load url's and .css file and extensions cause other issues

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