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
Describe the issue
I have a VM that was running MacOS 14. It was healthy and had no problems. I upgraded to MacOS 15 and this freeze-on-scroll behavior started. Any window seems to trigger it - Safari, firefox, settings app. The entire OS freezes for a couple seconds and then unfreezes.
It's not just the window that's being scrolled, because other windows such as terminal log tailing will freeze, too. VM has plenty of memory and disk space. I even tried increasing memory, but activity monitor shows the OS is no where near using all the allocated RAM.
Configuration
UTM Version: 4.5.4 (100)
macOS Version: Host: 14.6.1, Guest 15.0
Mac Chip (Intel, M1, ...): M1, 64gb host
Logs
I've looked through the logs, and the only suspicious entry is this, which is repeating over a hundred thousand times:
WindowServer Timer delayed by 77963.96s
WindowServer Timer delayed by 77963.96s
WindowServer Timer delayed by 77963.96s
Note the value is always the same unless I reboot.
Let me know what other logs that might be helpful. system.log didn't have anything notable.
The text was updated successfully, but these errors were encountered:
Describe the issue
I have a VM that was running MacOS 14. It was healthy and had no problems. I upgraded to MacOS 15 and this freeze-on-scroll behavior started. Any window seems to trigger it - Safari, firefox, settings app. The entire OS freezes for a couple seconds and then unfreezes.
It's not just the window that's being scrolled, because other windows such as terminal log tailing will freeze, too. VM has plenty of memory and disk space. I even tried increasing memory, but activity monitor shows the OS is no where near using all the allocated RAM.
Configuration
Logs
I've looked through the logs, and the only suspicious entry is this, which is repeating over a hundred thousand times:
Note the value is always the same unless I reboot.
Let me know what other logs that might be helpful. system.log didn't have anything notable.
The text was updated successfully, but these errors were encountered: