On my Mac mini (M1) with Big Sur 11.2.2 (20D80), some of the Finder integrations / extensions (Mountain Duck, HudahSpot, Adobe Core Sync helper, SetApp Finder Integration, ...) run multiple – after some time even dozens of – times. This sometimes slows down simple operations like login back in substantially.
Does this mean the finder crashes all the time silently in the background?
Mac mini 2018 or later
The only help we can provide, Bernd Goldschmidt, is that which we have already provided: you have something running that is not fully compatible with Big Sur.
The Finder Extensions are the primary suspects!
This will (almost certainly) not be solved by Big Sur updates, since the problem is not with Apple’s code.
Please, also see my recommendations for running an EtreCheck report, and providing a full copy thereof.
Bernd Goldschmidt wrote:
…
I doubt that the Finder Integrations are responsible. If I deactivate them all and kill all instances via force quit in the Activity monitor, I can reproduce the error with each one of them independently: Activating creates a running instance, deactivating them does not remove it. Activating again creates another instance each time.
You are responding in a way that suggests you do not understand what the problem is, and what we are trying to help you understand.
Simply deactivating a Finder extension will not, automatically, remove the running Finder extension: it will only -revert it from being run, in the future, so long as it is deactivated.
The fact that you see this misbehavior «with each one of them[Finder extensions] independently» indicates that either:
The following “Minor” issues should be checked on, carefully:
Both System modifications and Kernel extensions could be causing tour troubles. (Such will include your Finder extensions.)
Is you Epson printer software fully compatible with both Big Sur and M1? I’ve seen many people having trouble obtaining compatible Epson software (drivers).
Also check on your Wacom software.
The following Launch Agents: amazon.music, Setapp components, sucofyeh.agent, valvesoftware.steamclean, and homebrew. As well as the 1Password, Alfred, Better Mac Launch Helper, Deliveries Express, Drafts-OSX-Launcher, KeepingYouAwake Launcher, Menuwhere, Moom, PCalc Widget, Plex Media Server, BartenderStartAtLoginHelper, BusyCal, ChatMate for WhatsApp Setapp Helper, Default Folder X, DueAppLauncher, Focus, Gemini Menu Launcher, HazeOverLauncher, MindNode Helper, PDFSearchLoginHelperApp, PaletroLaunchHelper, PathFinderLauncher, LaunchAtLoginHelper, Trello Login Helper Login items.
The AdobeAAMDetect Internet Plug-in.
Your whole slew of Safari Extensions.
(Adobe software, as well. Also: Backblaze, Bombich, Dragan, DaisyDisk, Docker, MacroMates, Rogue Amoeba, Busy Apps FZE, Mozilla software.)
You may also need to check all your Apps that the EtreCheck report flagged with “High CPU Use”.
Disable those Extensions one at a time and re-check the activity.
Welcome, Bernd Goldschmidt, to Apple Support Communities!
It looks like you need to check all of those Finder Extensions for compatibility with both Big Sur and M1.
Incompatibility with either can cause any number of problems!
You should place you Kernel Panic log into the Extra Text of your message.
You should also run an EtreCheck (or EtreCheckPro) report, on your system, and, similarly, paste the plain-text version of its report into the Extra Text on a comment, here. See Using EtreCheck - Apple Community.
I ran EtreCheck but did not find anything suspicious
I doubt that the Finder Integrations are responsible. If I deactivate them all and kill all instances via force quit in the Activity monitor, I can reproduce the error with each one of them independently: Activating creates a running instance, deactivating them does not remove it. Activating again creates another instance each time.
I disabled all of them in the System Preferences and force quit all the entries in the Activity Monitor.
When I then enable any one of them, then disable and enable again, the picked integration will get another entry in the activity monitor for every time I enable it.
Disabling does not end the process. Enabling always adds another instance of the process.
All but Mountain Duck are shown with Architecture "Apple", so should be compiled for ARM/Apple Silicon and therefore compatible with Big Sur, right?
I disabled Mountain Duck for now and will monitor the situation.
Bernd Goldschmidt wrote:
All but Mountain Duck are shown with Architecture "Apple", so should be compiled for ARM/Apple Silicon and therefore compatible with Big Sur, right?
…
That would seem to be a reasonable expectation.
However, I recommend making sure you keep them up to date!
An update: I disabled and then even removed the Mountain Duck extension completely but the problem remains.
All the other finder extensions just multiply after some time.
Any more ideas?
I also had some hard crashes (Mac restarts without any interactions) and sometimes a when I do a normal restart I get a "Your Mac had to restart because of a problem" dialog box with content like this:
panic(cpu 3 caller 0xfffffe00158d9e90): watchdog timeout: no checkins from watchdogd in 301 seconds (24526 totalcheckins since monitoring last enabled), shutdown in progress
Debugger message: panic
Memory ID: 0x6
OS release type: User
OS version: 20D91
Kernel version: Darwin Kernel Version 20.3.0: Thu Jan 21 00:06:51 PST 2021; root:xnu-7195.81.3~1/RELEASE_ARM64_T8101
Fileset Kernelcache UUID: F78A48EC84D7C3283E7C6C67D00889A7
Kernel UUID: 9FE8C0DA-8ED0-381C-9CEC-2A779F3E1503
iBoot version: iBoot-6723.81.1
secure boot?: YES
Paniclog version: 13
KernelCache slide: 0x000000000ae68000
KernelCache base: 0xfffffe0011e6c000
Kernel slide: 0x000000000b99c000
Kernel text base: 0xfffffe00129a0000
Kernel text exec base: 0xfffffe0012a68000
mach_absolute_time: 0x55c7b5c1ffa
Epoch Time: sec usec
Boot : 0x604f4f4a 0x000999c1
Sleep : 0x00000000 0x00000000
Wake : 0x00000000 0x00000000
Calendar: 0x60530eae 0x000d625e
…
Any ideas?
Additionally, in the middle of the night, WindowServer crashes sometimes:
Termination Reason: WATCHDOG, [0x1] monitoring timed out for service
Termination Details: WATCHDOG, checkin with service: WindowServer returned not alive with context:
unresponsive work processor(s): WindowServer main thread
40 seconds since last successful checkin, 3692 total successsful checkins since load (0 induced crashes)
corebrightnessd, too:
Crashed Thread: 2 Dispatch queue: BacklightControl - Primary
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Application Specific Information:
dyld3 mode
*** Terminating app due to uncaught exception 'NSGenericException', reason: 'SkyLight offline - restart corebrightnessd'
terminating with uncaught exception of type NSException
abort() called
Still ongoing.
After running my Mac for less then three days all three of the mentioned finder integrations have more than 340 instances running.
The only remedy is always to restart the Mac.
Any more ideas what could be happening here?
Finder Integrations running multiple times (M1 Mac mini, Big Sur)