Previous 1 7 8 9 10 11 Next 180 Replies Latest reply: Mar 19, 2015 4:06 AM by Laura Malick Smith Go to original post Branched to a new discussion.
  • Eric Hildum Level 2 Level 2 (265 points)

    It is quite clear that the slow finder population has several causes. I will repeat that people should report the issue they encounter in a bug report to Apple with a System Report and sysdiagnose of Finder. In addition, if they find a work around, also let Apple know what it was.

     

    I have seen suggestions that one or more of the following contribute to the problem or solution:

    1. corrupt index, fixed by running the command sudo mdutil -E -a from Terminal

    2. Changing scrolling settings (see postings above)

    3. Changing DNS servers to more responsive servers.

    4. ensuring that all shared volumes are accessable (Finder blocks on network access?)

     

    Your results may vary. Clearly, the observed symptom of slow Finder can be caused by many issues, which makes identifying and solving the problem(s) much more difficult.

     

    System Reports can be generated from the detailed information in About this Mac, system diagnostics can be generated by running sudo sysdiagnose Finder from Terminal. The system diagnostics will supply the most information if they are obtained while the problem manifests. (That is, run it while you see slow population, not after.)

  • Bob_H Level 1 Level 1 (0 points)

    What does DNS have to do with Indexing... Is this a back handed way of saying without our permissions indexes are beig passed to Apple or some other entity?

     

    BTW, everythiing works until a reboot occurs... then it's back to square 1....

     

    Has Apple weighed in on tis issue...

  • icon mike Level 1 Level 1 (0 points)

    Try this link...

     

    http://osxdaily.com/2013/11/13/fix-finder-slow-high-cpu-use-mac-os-x/

     

    If you know how to get to the library folder (Go To Folder... ~/Library) and force quit (Force Quit... Relaunch Finder), you can do this manually without using command line prompts. This seems to have worked for me.

     

    These other methods did not (scroll bars, etc...).

     

    Good luck!

  • Bob_H Level 1 Level 1 (0 points)

    Only works until there is a reboot.. Then back to Square 1. Thanks for the input.. You never know what will fix this isse.

  • icon mike Level 1 Level 1 (0 points)

    Ahh, no, I haven't rebooted yet. Will try that and see what happens. Also, did you trash all com.apple.finder.XXX files? Also, check your activity monitor like the article says and see if it is once again taking up a ton of CPU. Will see if I can find something...

  • brilor Level 1 Level 1 (20 points)

    icon mike wrote:

     

    Try this link...

     

    http://osxdaily.com/2013/11/13/fix-finder-slow-high-cpu-use-mac-os-x/

    If deleting the finder property list works for you than you don't have the problem discussed on this thread. All the obvious attemps ( safe boot, clean OS X installl, deleting caches, running cleaning utiltites, deleting potentially corrupt plists etc.etc. ) don't work.

     

    Please read the entire thread and try Snaggletooh_DE's workaround. If it works for you than collect the diagnostics ( as outlined several times by Eric Hildum ) and send them to Apple and send them feedback

     

    APPLE DOES NOT MONITOR THESE LISTS. Posting here only allows other users to help you. It does NOT notify Apple.

  • brilor Level 1 Level 1 (20 points)

    Bob_H wrote:

     

    Has Apple weighed in on tis issue...

    Please read the entire thread and try Snaggletooh_DE's workaround. If it works for you than collect the diagnostics ( as outlined several times by Eric Hildum ) and send them to Apple and send them feedback

     

    APPLE DOES NOT MONITOR THESE LISTS. Posting here only allows other users to help you. It does NOT notify Apple.

  • icon mike Level 1 Level 1 (0 points)

    Sorry. Replied to the wrong thread.

  • Bob_H Level 1 Level 1 (0 points)

    Thanks for you ever so helpful response, this is forum to to share ideas and ask questions.

     

    I have alreday submitted the data to apple, I was hoping perhaps someone who submitted info before I did may have gotten feedback.

  • Eric Hildum Level 2 Level 2 (265 points)

    Bob_H wrote:

     

    What does DNS have to do with Indexing... Is this a back handed way of saying without our permissions indexes are beig passed to Apple or some other entity?

     

    BTW, everythiing works until a reboot occurs... then it's back to square 1....

     

    Has Apple weighed in on tis issue...

    I see I am wasting my time in ASC. Too many tin foil hat people here.

     

    Indexing issues might affect Finder, as will DNS issues if Finder is trying to list the contents of a remote volume. That does not mean that Apple has any interest in your particular Index.

  • zer0ed Level 1 Level 1 (0 points)

    Apple released the second beta build OS X 10.9.2 to developers today, nearly a month after the first beta was released. Developers can grab Build 13C39 from the Mac Dev Center, or by running a software update if you’re already running the first beta.

    The seed notes don’t list any new features, but ask devs to focus on Mail, Messages, graphics drives, VoiceOver, VPN and SMB2. The last beta added FaceTime over audio to the Messages and FaceTime apps.  Apple also seeded the first beta of Safari 6.1.2 to developers that looks like it’s mostly filled with bug fixes.

     

    Bet we still don't have a fix!

  • Bob_H Level 1 Level 1 (0 points)

    Sorry you think your wasting your time. Thanks for the response, I tried all the recommened fixes in this thread and others and wind up with the same issue after a reboot.

     

     

    I have sent multiple reports to Apple after quite a number of "MDWORKER" crashes.  each time I get multiple MDWORKER crahses after running "sudo mdutil -E -a"

     

    After attepting this:

    1 - Kill "com.apple.IconServicesAgent" using Activity Monitor

    2 - In Finder go to "Go to folder" under "Go" menu and paste: ~/Library/Caches/

    3 - Delete "com.apple.finder" (save a copy as backup if you want)

    4 - KillAll Finder

     

    Seems to be better.

     

    This is the last thing I tried: ( I apologize to the author of the followinf, I con't find the link for this suggestoion)

    sudo vi /etc/auto_master

     

    # Automounter master map

    #

    +auto_master            # Use directory service

    # /net                  -hosts          -nobrowse,hidefromfinder,nosuid

    /home                   auto_home       -nobrowse,hidefromfinder

    /Network/Servers        -fstab

    /-                      -static

     

    Commented out the /net line

     

    Tried:

    sudo automount -vc

     

    but automount was not found...

     

    I rebooted ans so far Finder seems to be working, no delays in providing directory lists.

     

    Given Automount is missing, I may have other issues, may try the full clean reinstall of Mavericks

     

    I also "fixed Permissions" on the disk, seemd iBooks had quite a number of bad settings.

  • TommyWillB Level 1 Level 1 (10 points)

    Okay, so I did a little test. Under sharing > options, I toggled AFP off and SMB on... and the reversed it.

     

    I connected from another computer on the same network and AFP seems decidedly FASTER.

     

    So, I'm going to keep SMB off to see if this helps longer term....

  • MikeB1969 Level 1 Level 1 (0 points)

    Tommy,

     

    Your suggestion indeed works. I left both AFP and SMB on, without even bothering to share any of the contents, and the speed of opening folders on our SBS increased instantly.

     

    Still to fight the battle with constantly losing my wireless connection, but at least one solution found.

  • Kenneth Collins1 Level 1 Level 1 (5 points)

    I have found a partial solution. The main symptom for me was that Finder took a nap while I was using the arrow keys to move around the files in a folder. I tried a different account on my computer, and Finder worked fine. That means that whatever my problem was, it was in the Library folder for my account.

     

    Back in my normal account. I searched the Library folder for name:Finder. The following two folders were in the list, but were not on the other Mac.

     

    com.apple.finder.legacy.mdlables

    com~apple~finder

     

    I deleted both files, and that has solved the immediate problem. However, it created a strange problem that is not all that bad. If I use the killall Finder command in Terminal or use Force Quit to relaunch Finder, it shuts down but does not relaunch. Clicking on the Finder icon in the Dock fixes that. I also cannot type in Launchpad to find an appplication, but that might be separate.

Previous 1 7 8 9 10 11 Next