Hello, I am also affected by this problem. and the first step will be figuring out which factors (both host configuration and VM configuration) contribute to the problem. We won't know which is true until we get to the bottom of this. ![]() It could either be that Fusion is doing something wrong all along, and we have been lucky up until macOS 10.15.6, or it could be that Fusion is doing something innocent and is triggering a new defect in macOS 10.15.6. Here, we have another case where everything was working fine before macOS 10.15.6, and now we see multiple users reporting this problem with macOS 10.15.6, and anecdotal evidence suggesting that Fusion is somehow involved. And if you didn't hit the exact conditions (at least 2 GBytes of RAM assigned to the VM, less than 32 GBytes of physical RAM in the host, and macOS 10.14.6, and with the problem substantially worsened by running an encrypted VM) then everything would work just fine. In this case, it was not anything wrong in Fusion, but something that Fusion did – and very few other applications would ever do – just happened to trigger the defect in macOS. Let's see if anything will change.ĭroark42 is just saying that the problem could be a new regression in the host OS, kind of like the one we saw over in VM became extremely slow after upgraded to macOS 10.14.6 , where VMs with more than 2 GBytes of virtual RAM running on hosts with less than 32 GBytes of RAM started performing very very poorly after a macOS update. I'll try to turn off the VM when I go to bed. I disabled 3D acceleration long time ago. ![]() Kernel Extensions in process name corresponding to current thread: watchdogdīoot args: chunklist-security-epoch=0 -chunklist-no-rev2-devĭarwin Kernel Version 19.6.0: Sun Jul 5 00:43: root:xnu-6153.141.1~9/RELEASE_X86_64 Service:, total successful checkins since load (148581 seconds ago): 14831, last successful checkin: 110 seconds agoīacktrace (CPU 2), Frame : Return Address ![]() Panic(cpu 2 caller 0xffffff7f845a1ad5): userspace watchdog timeout: remoted connection watchdog expired, no updates from remoted monitoring thread in 61 seconds, 7430 checkins from thread since monitoring enabled 148641 seconds ago after loadservice:, total successful checkins since load (148642 seconds ago): 14864, last successful checkin: 10 seconds ago Quite often when I wake up or leave workplace for a few hours, I see it shows a login screen and when I login, it restores all windows and shows that kernel panic message. This happens when I leave my MacBook Pro unattended. I realized there are have been a lot of reports like this since Catalina was released, but I only started having this issue when I installed 10.15.6 update. Graphics: kHW_AMDRadeonPro580Item, Radeon Pro 580, spdisplays_pcie_device, 8 GBĪirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x16F), Broadcom BCM43xx 1.0 (7.77.111.1 AirPortDriverBrcmNIC-1615.1)īluetooth: Version 7.0.6f7, 3 services, 27 devices, 1 incoming serial ports USB Device: FaceTime HD Camera (Built-in) USB Device: Bluetooth USB Host Controller Rip: 0x00007fff72dccdfa rfl: 0x0000000000000202 cr2: 0x00007fe347000018Ĭalls made by other processes targeting this process:Ĭalls made by all processes on this machine: Thread 0 crashed with X86 Thread State (64-bit): Thread 2:: -server 0 ?Ġx00007fff72dcce4e semaphore_timedwait_trap + 10 ![]() Unresponsive work processor(s): WindowServer main threadĤ0 seconds since last successful checkin, 3343 total successsful checkins since wake (0 induced crashes) Termination Details: WATCHDOG, checkin with service: WindowServer returned not alive with context: WATCHDOG, monitoring timed out for service Time Awake Since Boot: 37000 seconds Time Since Wake: System/Library/PrivateFrameworks/amework/Versions/A/Resources/WindowServer Didn't see it before, yes, there was WindowServer crash when the hang started: Process:
0 Comments
Leave a Reply. |