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

Catalina 10.15.6 keeps crashing

I have a problem. I updated to macOS 10.15.6 and now my system keeps crashing when I leave my computer for some time. Here is the crash report (some data removed for privacy concerns)


panic(cpu 2 caller ): userspace watchdog timeout: remoted connection watchdog expired, no updates from remoted monitoring thread in 69 seconds, 2219 checkins from thread since monitoring enabled 44430 seconds ago after loadservice: com.apple.logd, total successful checkins since load (44430 seconds ago): 4443, last successful checkin: 10 seconds ago
service: com.apple.WindowServer, total successful checkins since load (44400 seconds ago): 4431, last successful checkin: 10 seconds ago

Backtrace (CPU 2), Frame : Return Address
......
      Kernel Extensions in backtrace:
         com.apple.driver.watchdog(1.0)

BSD process name corresponding to current thread: watchdogd
Boot args: chunklist-security-epoch=0 -chunklist-no-rev2-dev chunklist-security-epoch=0 -chunklist-no-rev2-dev

Mac OS version:
19G73

Kernel version:
Darwin Kernel Version 19.6.0: Sun Jul  5 00:43:10 PDT 2020; root:xnu-6153.141.1~9/RELEASE_X86_64


Any idea what I can do? Please help, my system is unusable. I cannot restore my workspace every few hours when I leave my computer unattended.

MacBook Pro Retina

Posted on Jul 21, 2020 3:08 PM

Reply
Question marked as Best reply

Posted on Jul 29, 2020 10:11 AM

Days ago while debugging crashes I was pretty sure there was a memory leak (https://discussions.apple.com/thread/251610118). Here is what I am seeing now....


Imac27(Late 2103... 24GB ram)... No crashes since purging 32 bit applications. Running Activity monitor and watching memory allocations... Memory ramps up under heavy use, but is (Mostly) returned when apps quit... If system left logged in and unattended, memory slowly builds... but the system has enough ram to swallow it. When system logged out, memory cleaned up and next log in looks ok. Not like a fresh boot, but lots more memory available then prior to log out. Anecdotally I would say that WindowServer process is suspect, as it's memory allocation keeps growing.. Long running apps (Carbon Copy Cloner directing multi GB network backups) cause memory usage to ramp up. But system stays together. Unfortunately, the system that is the target of the network back up crashes.....


MacMini(Late 2012.... 16GB ram).... Under light use, no crashes after purging 32 bit applications. However, crashes still occurring under 2 cases.... When a usb drive attached to the mini is being used as the network target of a multi GB backup (>150GB), and when running VMware Fusion.


When the usb drive attached to the MacMini is the network backup target, the machine crashes after it receives about 130GB of backup data. Seems very repeatable. System just drops dead. Looked at logs... See nothing posted in log files for minutes on end, until hardware reset button initiates forced boot. I don't think that the process which causes the crash is caught by the OS before the system goes down...


When the MacMini is running VMware Fusion... have not established a pattern other than don't turn your back on it... We only run Win10 using Quickbooks in Fusion... Generally stays up for 15-20 minutes of use, allowing quick things to be done... if interrupted and leave the machine without logging off, will find it has crashed if not attended to within 60 minutes or so...Unlike the crash when the system is a backup target, this one seems totally random. Probably because VMware and Wind10 are pushing the system harder and in random directions.


My bottom line....


  1. if you are upgrading or have upgraded, purge all 32 bit apps and their companion crud... The system is not stable at all if a 32bit app or its agents or daemons gets touched. Absolutely huge difference in machine stability.
  2. Memory Leak Work Around..... Be very careful with long duration or cpu/memory intensive processes. While you are running them, run activity monitor and watch the 'Memory Used" number. If that approaches 60-70% of physical memory, be prepared to stop your process and log out to reset memory if you can. Lots of people are reporting crashes with VMware or Virtualbox.... but I suspect that other memory intensive apps would also be having the same problem, as I see it in a long duration process on a MacMini just accepting network data and writing to disk.
  3. Hope, keep your fingers crossed, practice what ever superstition works best for you.... and hope that APPLE fixes this bug quickly....



195 replies

Catalina 10.15.6 keeps crashing

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