You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First, I'm not entirely sure how useful this report will be.
I was experimenting with Yocto Project builds inside a krunvm on my M1 MBP (16GB RAM). About ten minutes into the build my pointer got very laggy, it started beachballing, and then the machine rebooted (on restart, the diagnosis was that the WindowServer watchdog timed out).
Yocto was building a whole Linux distro including the cross toolchain from scratch, so it's CPU and I/O heavy.
I started by blaming the combination of both, but when I went to delete the build tree (a good 30GB) it crashed again, so it looks like it's just heavy I/O.
FWIW, my krunvm guest was configured with 8GB of RAM and 6 cores.
The text was updated successfully, but these errors were encountered:
I'm curious if this is systematic? I have done some relatively heavy builds with my krunvm on my M1 mac, and I didn't run into that. Do you want me to try and reproduce?
Note that the Windows Server timeout is an ongoing issue with macOS, and I got it with many other workloads, including Google Meet. I filed at least three or four issues with Apple on this one. If you have an exact step by step reproducer, that could help Apple chase it down.
First, I'm not entirely sure how useful this report will be.
I was experimenting with Yocto Project builds inside a krunvm on my M1 MBP (16GB RAM). About ten minutes into the build my pointer got very laggy, it started beachballing, and then the machine rebooted (on restart, the diagnosis was that the WindowServer watchdog timed out).
Yocto was building a whole Linux distro including the cross toolchain from scratch, so it's CPU and I/O heavy.
I started by blaming the combination of both, but when I went to delete the build tree (a good 30GB) it crashed again, so it looks like it's just heavy I/O.
FWIW, my krunvm guest was configured with 8GB of RAM and 6 cores.
The text was updated successfully, but these errors were encountered: