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

Aug 18, 2020 11:02 AM in response to akashthomas43

As I said in my previous post, Windows 10 is the answer. I have a brand new Macbook Pro, the most expensive laptop I've ever owned. But I also own a couple of other laptops that run Windows 10 which are several years old and none of them ever crashed, not even once in all those years. What I'm doing now is completely wiping my MacBook Pro and installing Windows 10 on it. I have been running Windows 10 on one partition with bootcamp and that never had a problem. The crashes only occur on the Mac side, which proves it's not a hardware issue but has something to do with the utter incapability of the Apple developers to produce a flawless operating system. While I still like the Apple Hardware, the software is an absolutely catastrophe. My recommendation to the Apple developers: go and take an internship at Microsoft and learn how to do stuff right!

Aug 18, 2020 5:12 PM in response to alekseyfromsan francisco

Updated to 10.15.6 Supplemental and my kernel panics have stopped. I have some other somewhat unusual behavior such as a lot of fan activity and the fact that my iMac monitor will not go into “off” mode no matter what the power saving settings are. Other than that the supplemental has handled the major issue and I am hoping that Big Sur will take care of the other odd behaviors. I am running both VMWare Fusion and Parallels 16.

Aug 18, 2020 5:30 PM in response to obscurebug

Actually the monitor of my iMac no longer shuts off after the elapsed time. I have unchecked the wake on LAN setting. The screen saver kicks in as expected it is just the monitor that does not time out and turn off. I will check out the “Preventing Sleep” section of Activity Monitor as you suggested. Thank you for your response.

Aug 18, 2020 7:52 PM in response to JimInVA

Okay, I agree to what you and others have said and I will stop ranting. But I am just extremely frustrated that I can't find a solution to my Kernel Panic issues. I even spent a long time with Apple support on the phone and they had me reinstall my entire operating system. But the issues just came back. But I agree with what you say, that just letting off steam doesn't help anyone. So no worries, I'll keep my mouth shut for now and just hope the OS issues get fixed some time soon.

Aug 19, 2020 12:37 AM in response to frtzn

As there are at least three different kinds of kernel-panic related problems discussed in this thread, it might me a good idea to always specify which of these problems you have or had:


1. A memory leak that leads to reproducible freezes/crashes/kernel panics especially when certain VM software is used.

--> The Supplemental Update should have fixed this.


2. An issue that causes random kernel panics, even when no apps are running and the Mac is on idle (often late at night).

--> The Supplemental Update seems not to have fixed this.


3. Crashes on wake up after system sleep.

-->The Supplemental Update seems not to have fixed this.

Aug 24, 2020 1:20 AM in response to frtzn

I have Microsoft Office... however, I think the culprit is more likely to be my external disk drives - 5 in a caddy. When they were disconnected my iMac did not crash at all. Initially I thought it was a thunderbolt connection issue, and moving to a USB connection seemed to make the crashes less frequent, but they still happened. The exception was for the 24 hours or so that I left one disk connected and copied the data to a NAS - no crash while the disk was active.


Aug 25, 2020 10:32 PM in response to alekseyfromsan francisco

updated my MacBook 16 pro - got this in June. updated to this maybe earlier this week. now when unattended for perhaps 30 mins or so, it restarts due to an issue but no app would be running. Now my TouchBar is completely off - it does not even recognize i have a touchbar in my system preferences.


so i factory reset the Mac and boom issue fixed.

but same thing happened - Crashed - Restarted due to an issue - and TouchBar once again OFF - no way around it. this update really caused it.


excuse the bad grammar - i am just frustrated. got an appointment for service nearby and at authorized dealer since apple stores are closed right now in LA Area. i really just think its this Update. really did a number here.

Aug 26, 2020 3:32 PM in response to cesar1191

I had the same exact word for word issue. I brought it into apple, and my laptop, the 13 inch 2017 model is still under the keyboard replacement program, so they replaced my Touch Bar for me under that warranty, and it just came back, in perfect condition. So far the Touch Bar is working and my sleep is functioning as well. So I genuinely believe that the issue is a Touch Bar/Keyboard issue if everyone else is having this occur with their Touch Bar MacBook. It makes sense because the Touch Bar is always functioning, so it could have something to do with the kernel and that maybe.

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.