hatotoro
Level 1 (0 points)

Q: Yosemite: tagging cause Finder to freeze

Hello,

 

I have this weird problem since Yosemite. Everytime I ‘tag‘ something my Finder starts freezing for 5 to 7 minutes. I tried the PRAM thing, and reinstalled Yosemite but nothing solved this problem, so here i am.

 

I think i am the only one that has this problem, because google didn‘t found something similar. So hoping for some help.

MacBook Pro (15-inch Mid 2009), OS X Yosemite (10.10.3)

Posted on May 26, 2015 2:09 PM

by Linc Davis,Solvedanswer
Linc Davis Linc Davis
Level 10 (208,037 points)
Applications
A:

Please sign out of iCloud in its preference pane and see whether there's any change. No data will be removed from the servers, and you can retrieve it by signing back in. That said, you should always have a current archive of the data for safety's sake, even if you don't sign out.

If you use iCloud Keychain, when you sign back in to iCloud follow one of the procedures described in this support article to set it up on an additional device.

Posted on May 27, 2015 9:43 AM

Close
hatotoro

Q: Yosemite: tagging cause Finder to freeze

  • All replies
  • Helpful answers

  • by Linc Davis,

    Linc Davis Linc Davis May 26, 2015 3:38 PM in response to hatotoro
    Level 10 (208,037 points)
    Applications
    May 26, 2015 3:38 PM in response to hatotoro

    Back up all data.

    Open the Library folder in your home folder by holding down the option key and selecting

              Go ▹ Library

    from the Finder menu bar. From the Library folder, move the following folder to the Trash, then relaunch the Finder and empty the Trash

              Caches/com.apple.finder

    Test. If there's no improvement, move each of these files to the Desktop:

              Preferences/com.apple.finder.plist

              Preferences/com.apple.recentitems.plist

              Preferences/com.apple.sidebarlists.plist

              Saved Application State/com.apple.finder.savedState

              SyncedPreferences/com.apple.finder.plist

    Log out, log back in, and test. If there's no change, put each file you moved back where it was, overwriting the one that may have been created in its place, and log out again. Otherwise, delete the files you moved.

  • by hatotoro,

    hatotoro hatotoro May 27, 2015 2:18 AM in response to Linc Davis
    Level 1 (0 points)
    May 27, 2015 2:18 AM in response to Linc Davis

    Hello Linc Davis,

     

    First, thank u for some thoughts. I tried it, but still have the same problem … it is really only the Finder that freeze, i can still work with other Apps.

  • by Linc Davis,

    Linc Davis Linc Davis May 27, 2015 6:00 AM in response to hatotoro
    Level 10 (208,037 points)
    Applications
    May 27, 2015 6:00 AM in response to hatotoro

    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 and start typing the name.

    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.

    Click the Clear Display icon in the toolbar. Then take the action that isn't working the way you expect. Select any lines that appear in the Console window. Copy them to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.

    The log contains a vast amount of information, almost all of which is irrelevant to solving any particular problem. When posting a log extract, be selective. A few dozen lines are almost always more than enough.

    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.

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

    When you post the log extract, 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.

  • by hatotoro,

    hatotoro hatotoro May 27, 2015 6:23 AM in response to Linc Davis
    Level 1 (0 points)
    May 27, 2015 6:23 AM in response to Linc Davis

    Thank you again for responding, here is the Log from Console after adding a «tag» to a picture:



    27.05.15 15:10:14.462 Finder[539]: <TTaggingTokenFieldCell: 0x6000007f9500>: Failed to query display string for a represented object <TTagInfo: 0x60800065dc40>. Ignoring...

    27.05.15 15:10:14.732 coreservicesd[129]: SFLEntryBase::ListHasChanged mach_msg returned 10000004d

    27.05.15 15:10:27.302 spindump[404]: Saved spin report for Finder version 10.10.4 (10.10.4) to /Library/Logs/DiagnosticReports/Finder_2015-05-27-151027_USER-MacBook-Pro.spin

     

    27.05.15 15:10:48.370 Finder[539]: lock contention for shared file list item 0x60000077d580

     

    27.05.15 15:12:54.000 kernel[0]: process Finder[539] thread 17493 caught burning CPU! It used more than 50% CPU (Actual recent usage: 92%) over 180 seconds. thread lifetime cpu usage 162.767427 seconds, (159.552208 user, 3.215219 system) ledger info: balance: 90004010905 credit: 162494064099 debit: 72490053194 limit: 90000000000 (50%) period: 180000000000 time since last refill (ns): 97070297204

    27.05.15 15:12:54.669 com.apple.xpc.launchd[1]: (com.apple.ReportCrash[556]) Endpoint has been activated through legacy launch(3) APIs. Please switch to XPC or bootstrap_check_in(): com.apple.ReportCrash

    27.05.15 15:12:54.670 ReportCrash[556]: Invoking spindump for pid=539 thread=17493 percent_cpu=92 duration=98 because of excessive cpu utilization

    27.05.15 15:12:55.119 spindump[404]: Saved cpu_resource.diag report for Finder version 10.10.4 (10.10.4) to /Library/Logs/DiagnosticReports/Finder_2015-05-27-151255_USER-MacBook-Pro.cpu_r esource.diag

     

    27.05.15 15:15:10.013 com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.

    (This was the last line before the freezing stopped.)

  • by Linc Davis,

    Linc Davis Linc Davis May 27, 2015 6:33 AM in response to hatotoro
    Level 10 (208,037 points)
    Applications
    May 27, 2015 6:33 AM in response to hatotoro

    Please read this whole message before doing anything.

    This procedure is a diagnostic test. It’s unlikely to solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.

    The purpose of the test is to determine whether the problem is caused by third-party software that loads 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, if applicable. Start up in safe mode and log in to the account with the problem.

    Note: If FileVault is enabled in OS X 10.9 or earlier, or if a firmware password is set, or if the startup volume is a software RAID, you can’t do this. Ask for further instructions.

    Safe mode is much slower to start up 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 startup may also be somewhat slow.

    The login screen appears even if you usually login 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, restart as usual (not in safe mode) and verify that you still have the problem. Post the results of the test.

  • by hatotoro,

    hatotoro hatotoro May 27, 2015 9:37 AM in response to Linc Davis
    Level 1 (0 points)
    May 27, 2015 9:37 AM in response to Linc Davis

    So I did what you demand, so I unplugged everything, started up in SafeMode.

    Problem is still there. So while I tagged a picture, I watched for changes in the Activity Monitor. So while writing the Tag nothing special is happening, but after hitting the «Enter» Key to confirm, the CPU rocks sky high -> 127%, when it goes down after a while the spinning stops.

     

    So, I downloaded the Tagit App to test if the tagging cause the high CPU, or something causing the Finder to get kill himself because he don't like tags. Testing  the Tagit App and it handle the «tags» without any problem, there are no delay, and the CPU is normal.

     

    I just prefer the Finder because of the workflow, in Tagit App you have to drag&drop it everytime. But when there is no solution … .

     

    I really think the problem is deeper, it‘s like a canyon without a bridge to cross over, so you have to go around, that needs more time and energy, like the Finder (CPU 127%).

  • by Linc Davis,Solvedanswer

    Linc Davis Linc Davis May 27, 2015 9:43 AM in response to hatotoro
    Level 10 (208,037 points)
    Applications
    May 27, 2015 9:43 AM in response to hatotoro

    Please sign out of iCloud in its preference pane and see whether there's any change. No data will be removed from the servers, and you can retrieve it by signing back in. That said, you should always have a current archive of the data for safety's sake, even if you don't sign out.

    If you use iCloud Keychain, when you sign back in to iCloud follow one of the procedures described in this support article to set it up on an additional device.

  • by hatotoro,

    hatotoro hatotoro May 29, 2015 12:57 AM in response to Linc Davis
    Level 1 (0 points)
    May 29, 2015 12:57 AM in response to Linc Davis

    Yes it was the iCloud Drive that cause all this problems.

     

    I don't have the link right now, because i reinstalled yosemite again. But kind of people solved this problem by deleting the «com.apple.sidebarlists», or unchecked all Tags in the Finder sidebar so their not showing, for me this doesn't work.

    So, like you said, i first signed out of iCloud especially iCloud Drive, the same thing i did on my iPhone. I reinstalled Yosemite without login to iCloud. I can now Tag without problems.

     

    Thank you very much Linc Davis for the time and thoughts.