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

after encrypting with filevault 2 on mountain lion, safari is extremely slow

after encrypting with filevault2 on mountain lion, safari is running extremely slow.


it's taking more than 45 seconds (sometimes a full minute) to load pages.


my internet speeds are 35 mbps download and 6.35 mpbs upload, so it's not my internet connection.


i have deleted the cache files and the system preferences.


i'm finding that chrome is faster, but i'm seeing slowness there too.


in encrypted using filevault 2.0 yesterday, all software is up to date.


can anyone please help me with this? i don't want to have to turn off filevault.


thanks!

Mac mini, OS X Mountain Lion, mac mini, 16 GB RAM, 512 SSD

Posted on Aug 3, 2012 7:27 PM

Reply
35 replies

Aug 3, 2012 9:44 PM in response to Linc Davis

that's not accurate, and since deactivating FileVault resolved the issue, that means that it was so something in the encryption that caused the issue. there's not too much troubleshooting that could be done beyond what I had already done anyway. I'm going to turn it back on and see if the issue returns.


incidentally, none of my other devices or my MacBook air are experiencing any slowness online, so it's definitely not the internet connection.

Aug 4, 2012 8:29 AM in response to lbk.lbk

ok, troubleshooting steps taken, stil having the issue of incredible slowness with safari:


turned off filevault (which looks like it had nothing to do with it, although the issue started after turning filevault on, so it's possible that the encryption caused some kind of corruption somewhere)


deleted ~/Library/Caches/


deleted all ~/Library/Preferences/ (made a copy of them first, this did nothing so i put them back)


turned off all safari extensions


deleted ~/Library/Preferences/com.apple.safari.plist


reset safari (althought after doing those other things first, i'm not sure what that is going to do)


the issue still persists.


please advise.


thank you.



Aug 4, 2012 8:32 AM in response to lbk.lbk

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 4, 2012 10:55 AM in response to lbk.lbk

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 4, 2012 12:22 PM in response to Linc Davis

Last login: Sat Aug 4 08:53:47 on console

lisas-Mac-mini:~ lisaxxxxx$ find . $TMPDIR.. \( -flags +sappnd,schg,uappnd,uchg -o ! -user $UID \) -ls

333785 8 -rw-r--r-- 1 root lisaxxxxx 160 Jul 20 2009 ./.yawpycrypto.rnd

2640311 280 -r-sr-xr-x 1 root lisaxxxxx 140536 Jul 18 2007 ./Library/Application Support/MoreSecurityTest/HelperTool

397023 8 lrwxr-xr-x 1 root lisaxxxxx 15 Feb 4 2009 ./Library/Favorites/Documents -> ../../Documents

lisas-Mac-mini:~ lisaxxxxx$

Aug 4, 2012 12:34 PM in response to lbk.lbk

You have an SUID root executable from an outdated Apple developer tool in your home directory. It's been there for five years. You also have a hidden root-owned data file from a Python module, which has been there for three years. Do you know about those items? They probably aren't related to your problem, though I can't be sure.

after encrypting with filevault 2 on mountain lion, safari is extremely slow

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