TotalFinder hangs (or crashes) Finder at startup

Disabling only Tabs plugin has solved the problem.

1 Like

Ok, the problem is somewhere in the Tabs plugin. Thanks for narrowing it down.

@werdy It would be great if you could send me the file /Library/Logs/DiagnosticReports/Finder_2014-07-04-104901_Werdys-Macbook-Pro.cpu_resource.spin to support@binaryage.com. It could tell where exactly is Tabs code spending the CPU time.

@darwin Sent.

In that report there were two active plugins in memory, Tabs and ColumnViewAutoWidth. Could you do another test, just with Tabs enabled?

Also I have one additional tweak to try.

Enable only Tabs plugin. Make sure the issue is reproducible. Then set this tweak and restart Finder + TotalFinder again.

defaults write com.apple.finder TotalFinderDisableCrashInfo -bool yes

Only Tabs enabled it hanged:

    2014.07.04. 13:03:36,099 TotalFinder[573]: requesting injection into com.apple.finder[2688]
    2014.07.04. 13:03:36,416 Finder[2688]: TotalFinderInjector v1.6.1 received init event
    2014.07.04. 13:03:36,429 Finder[2688]: TotalFinderInjector: Installing TotalFinder ...
    2014.07.04. 13:03:36,430 Finder[2688]: Launching TotalFinderCrashWatcher from '/Library/ScriptingAdditions/TotalFinder.osax/Contents/Resources/TotalFinder.bundle/Contents/Resources/TotalFinderCrashWatcher.app'
    2014.07.04. 13:03:36,437 TotalFinder[573]: TotalFinder has been succesfully injected into com.apple.finder[2688]
    2014.07.04. 13:03:38,491 Finder[2688]: Skipping loading plugin ColorfulSidebar because it is disabled by plist switch TotalFinderColorfulSidebarDisabled.
    2014.07.04. 13:03:38,492 Finder[2688]: Skipping loading plugin ColumnViewAutoWidth because it is disabled by plist switch TotalFinderColumnViewAutoWidthDisabled.
    2014.07.04. 13:03:38,492 Finder[2688]: Skipping loading plugin CopyPathMenu because it is disabled by plist switch TotalFinderCopyPathMenuDisabled.
    2014.07.04. 13:03:38,492 Finder[2688]: Skipping loading plugin CutAndPaste because it is disabled by plist switch TotalFinderCutAndPasteDisabled.
    2014.07.04. 13:03:38,492 Finder[2688]: Skipping loading plugin DockProgressBar because it is disabled by plist switch TotalFinderDockProgressBarDisabled.
    2014.07.04. 13:03:38,492 Finder[2688]: Skipping loading plugin FoldersOnTop because it is disabled by plist switch TotalFinderFoldersOnTopDisabled.
    2014.07.04. 13:03:38,493 Finder[2688]: Skipping loading plugin Labels because it is disabled by plist switch TotalFinderLabelsDisabled.
    2014.07.04. 13:03:38,493 Finder[2688]: Skipping loading plugin NoDesktopDots because it is disabled by plist switch TotalFinderNoDesktopDotsDisabled.
    2014.07.04. 13:03:38,493 Finder[2688]: Skipping loading plugin SystemFiles because it is disabled by plist switch TotalFinderSystemFilesDisabled.
    2014.07.04. 13:03:38,494 Finder[2688]: Skipping loading plugin Visor because it is disabled by plist switch TotalFinderVisorDisabled.
    2014.07.04. 13:05:16,000 kernel[0]: process Finder[2688] thread 78498 caught burning CPU! It used more than 50% CPU (Actual recent usage: 80%) over 180 seconds. thread lifetime cpu usage 90.613343 seconds, (81.521489 user, 9.091854 system) ledger info: balance: 90001594441 credit: 90001594441 debit: 0 limit: 90000000000 (50%) period: 180000000000 time since last refill (ns): 112121656741 
    2014.07.04. 13:05:16,985 ReportCrash[2703]: Invoking spindump for pid=2688 thread=78498 percent_cpu=80 duration=113 because of excessive cpu utilization
    2014.07.04. 13:05:19,794 spindump[2704]: Saved cpu_resource.spin report for Finder version 10.9.4 (10.9.4) to /Library/Logs/DiagnosticReports/Finder_2014-07-04-130519_Werdys-Macbook-Pro.cpu_resource.spin

With crash info disabled hanged again (without crash info):

2014.07.04. 13:08:07,390 TotalFinder[573]: requesting injection into com.apple.finder[2710]
2014.07.04. 13:08:07,688 Finder[2710]: TotalFinderInjector v1.6.1 received init event
2014.07.04. 13:08:07,702 Finder[2710]: TotalFinderInjector: Installing TotalFinder ...
2014.07.04. 13:08:07,702 Finder[2710]: Disabled advanced crash info (defaults delete com.apple.finder TotalFinderDisableCrashInfo)
2014.07.04. 13:08:07,703 Finder[2710]: Launching TotalFinderCrashWatcher from '/Library/ScriptingAdditions/TotalFinder.osax/Contents/Resources/TotalFinder.bundle/Contents/Resources/TotalFinderCrashWatcher.app'
2014.07.04. 13:08:07,711 TotalFinder[573]: TotalFinder has been succesfully injected into com.apple.finder[2710]
2014.07.04. 13:08:09,763 Finder[2710]: Skipping loading plugin ColorfulSidebar because it is disabled by plist switch TotalFinderColorfulSidebarDisabled.
2014.07.04. 13:08:09,763 Finder[2710]: Skipping loading plugin ColumnViewAutoWidth because it is disabled by plist switch TotalFinderColumnViewAutoWidthDisabled.
2014.07.04. 13:08:09,763 Finder[2710]: Skipping loading plugin CopyPathMenu because it is disabled by plist switch TotalFinderCopyPathMenuDisabled.
2014.07.04. 13:08:09,763 Finder[2710]: Skipping loading plugin CutAndPaste because it is disabled by plist switch TotalFinderCutAndPasteDisabled.
2014.07.04. 13:08:09,764 Finder[2710]: Skipping loading plugin DockProgressBar because it is disabled by plist switch TotalFinderDockProgressBarDisabled.
2014.07.04. 13:08:09,764 Finder[2710]: Skipping loading plugin FoldersOnTop because it is disabled by plist switch TotalFinderFoldersOnTopDisabled.
2014.07.04. 13:08:09,764 Finder[2710]: Skipping loading plugin Labels because it is disabled by plist switch TotalFinderLabelsDisabled.
2014.07.04. 13:08:09,764 Finder[2710]: Skipping loading plugin NoDesktopDots because it is disabled by plist switch TotalFinderNoDesktopDotsDisabled.
2014.07.04. 13:08:09,764 Finder[2710]: Skipping loading plugin SystemFiles because it is disabled by plist switch TotalFinderSystemFilesDisabled.
2014.07.04. 13:08:09,765 Finder[2710]: Skipping loading plugin Visor because it is disabled by plist switch TotalFinderVisorDisabled.

I will send you cpu_resource.spin file in email for the first case.

Thank you very much.

Please test another tweak (with Tabs plugin enabled):

defaults write com.apple.finder TotalFinderDontRestoreTabsState -bool yes

And I would need one extra sample. Files you provided are ‘spin dumps’. I would like to see Finder.app process sample.

Please

  1. open Activity Monitor.app
  2. filter process list with “Finder” keyword
  3. sample Finder.app (not TotalFinder.app)

Hit the sample button when Finder is eating 100% only with Tabs plugin loaded. Send the sample file to my email. Thanks.

@darwin Sorry, but I can not send you spin dumps, as the bug is gone. I disabled tab state recovering as you wrote, run activity monitor and realized that TotalFinder and TotalFinderCrashWatcher were running (while icon on dock displayed only Finder). After I closed these processes and restart Finder TotalFinder worked as it should be. I reenabled all the plugins and still working. Did tab state restoring cause the hangs?

This solved the problem!!

I can confirm that this fixes the problem with all plugins enabled.

I’m back! Good news is that we have a workaround now and we have isolated the issue pretty well.

I’m looking into my source code and changes which could have caused the problems. But I don’t see any obvious culprit.

It would be great if someone who is able to reproduce the issue could go back and install previous beta versions and tell which version started to exhibit the wrong behaviour:
http://totalfinder.binaryage.com/beta-changes

Hi,

I installed 10.9.4 this morning and the problems being described started after the update. I have uninstalled TotalFinder and reinstalled and that did not fix the problem 1.6. I have read through the thread above and see that it could be the Tabs causing the issue. I do use the TotalFinder tabs, one of the best parts of the product. Okay, with that being said, what I am seeing in Activity Monitor is Finder is using a lot of RAM, like it has a memory leak. This is with TotalFinder running, sort of running, if you will, it’s started but I cannot open TotalFinder. When I double click the icon it does nothing. Both TotalFinder the Watch process are running and not using much RAM. Seems to be a integration or compatibility issue between native Finder and TotalFinder. Thought may be this information would be helpful to the remediation of the issue being seen.

To add, and almost forgot, after I rebooted at one point with 1.6 installed I was working on something else, and an update did popup to install 1.6.1 and that did not resolve the problem. I get the same results as described above. I have to force quit Totalfinder for my machine to run normally. otherwise it is very slow and it starts using a lot of RAM. Once i force quit Totalfinder I drop back down below 3GB of RAM. My iMac has 12GB installed. With Totalfinder started I find Finder will get to 8GB and then drop back down to over 6GB and climb again.

Hopefully more useful information?

Thanks,
Erick

I also tried uninstalling TotalFinder and reinstalling 1.6.1 without doing the 1.6 to 1.6.1 update and that didn’t help things either. Note after I try to start TotalFinder it just hangs will not open and my CPU and memory for Finder just climbing and Finder ends up showing that it is not responding so I have to relaunch it and then CPU and Memory go back to normal. Plus this time I noticed that User Agent for TotalFinder is not responding either.

More info.

Thanks,
Erick

This problem is literally driving me CRAZY. Can we please gets a walk-through of how to solve the issue? My FINDER has been screwed up for nearly two weeks now and its hard to even do work.

??? Im imagining that if there are this many posts on this problem that there are exponentially more people effected by this.

Its seems to be the TotalFinderCrashWatcher that is having problems.

I’m going to release new TotlaFinder 1.6.2 on beta channel this weekend. I hope to solve it, but still without reproducible case, it is just guesswork.

I’ll video share my screen with you… tell me what you need to see. I’ve uninstalled TotalFinder and the problem still remains. Seems like TotalFinder screwed up regular finder some how.

TotalFinder 1.6.2 beta is out:
http://totalfinder.binaryage.com/beta-changes#1.6.2

I did review of the code and made whole process of restoring previous tabs more reliable (changed timing and sequencing of individual operations). But I still don’t know if this could potentially fix the issue.

Please test and report here. Thank you.

I was having these issues (maybe not as severe as others), but now TotalFinder is very snappy on launch. Thank you!

1 Like

1.6.2 still didn’t resolve the problem for me. To be clear, I have uninstalled any prior version and installed 1.6.2 and that didn’t help. I have also uninstalled 1.6.2 and tried reinstalling it from scratch that didn’t help either.

This is what I am see occur while monitoring with Activity Monitor. Once Totalfinder starts up it causes Finder to start using 99.8% to 100% of the CPU and the amount of memory starts growing, it also shows Finder as Not Responding. I let it run for about 10 minutes to see if it would shake out and come back down in CPU and Memory and it didn’t. However, finder did not report as Not Responding any longer. But to be clear it was still using 100% of CPU. I had to right click on the Finder/TotalFinder icon on the dock to relaunch Finder. This caused CPU and Memory to drop to normal again. I am again running 10.9.4. For me this problem started with 10.9.4 and I was running TotalFinder 1.6. Something about Finder has changed as I have never had any issues with TotalFinder updates in the past. I am wondering if something meant for Yosemite has found it’s way into TotalFinder for Mavericks? Just throwing that out there. Very frustrating problem though, I miss using TotalFinder, it made Finder what it should be.

Hope this info is helpful in some way.

Thanks,
Erick