WindowServer crashing repeatedly since upgrade to Ventura

Experiencing the exact same issue since macOS Ventura Update.

MacBook Air (13 inch, 2021, M1).

I am currently using an external monitor as "main display" and some apps in full screen mode.

Could not identify if the crash was during cmd+tab alternation.

Unfortunately, the 13.0.1 update didn't resolve this crashing problem for me. WindowServer still crashes randomly... although for me notably when my machine wakes from standby (opening my notebook's lid).

Yes, I've had exactly the same symptoms since installing Ventura (13.0.0, then 13.0.1). My crashes are every few hours, approximately once per day.

I've been using one external display. This happens most frequently when I switch desktops on the external display. In about 10% of the crashes, I wasn't switching desktops on the external display.

The same here :

MacBook Pro 13 Inch M1 , 2020

Since Ventura 13.0

I connected two external Monitors via HDMI with a Hub hhttps://hypershop.zendesk.com/hc/en-us/articles/9342831058708-macOS-Ventura-Update-Troubleshooting

They even have a trouble shooting guide https://hypershop.zendesk.com/hc/en-us/articles/9342831058708-macOS-Ventura-Update-Troubleshooting

This helped for a couple days at most , couple of hours at least, but not really a solution.

Then i used only one Monitor ... same

Also not using the internal Display only ....

My solution: i switched my "older" caldigit usb-c pro dock, which only supports one Monitor as native the M1 Chip 2020. That seems to work....

It's happened consistently since I upgraded to Ventura (never happened before). It seems to happen ONLY when I run an app in full screen mode (I have two external monitors attached to my Mac mini 2018). It crashes everything except the Apple applications (Mail, Calendar) and locks the screen.

I avoided full screen apps for 3 or 4 days and had no issues. As soon as I went full screen with an app (not an Apple app), I crashed within 5 minutes.

The problem occurs in both 13.0 and 13.0.1.

A couple of days ago, I hypothesized that the crashes are caused by some sort of race condition: for example, some in-memory structure gets used before it's fully constructed. And based on the evidence, it seems that the condition happens when switching apps on an external monitor. I'm not completely sure, but I think the condition also might depend on switching desktops.

To test this, I've modified my behavior a bit for the past couple of days. Instead of switching apps as fast as I like, when I use command-tab, I choose the app that I want, then I hold it for a moment to make sure all displays on my current desktop are fully updated. Then I let go.

So far, no crashes.

This might be interesting as a workaround and as a diagnostic observation. I can't claim that this is real cause and effect and don't want to create a superstition :) but thought I'd share here, since we're grasping at straws.

FTR: I'm still on 13.0.1. (At time of writing, there is no 13.0.2.)

Given that a lot of people are reporting issues with using multiple monitors causing this issue, this made me look at how at how I use desktops as part of my usual routine. Instead of opening my Music library on a separate desktop, I am now using just the one desktop to do everything. It has only been 1 day or so, but no crashes as all and usually have 3-4 a day. Keeping my fingers that this works until Apple gets this addressed.

I've had no crashes since I wrote that three days ago, and have been using my machine heavily with external monitors. I'm getting more and more confident in the race-condition theory.

On a practical level, it means using command-tab slowly, as I described above: "I hold it for a moment to make sure all displays on my current desktop are fully updated. Then I let go."

This is getting ridiculous, my MacBook Pro 2019 connected via usbC to Dell 4k, crash 3 to 5 times per day. most of the time after using screen saver or adding/removing a 2nd monitor Hdmi.

After a crash and a fresh start, sometime i have only black screen. so i have to unplug all usb C and restart again... what a mess

PS : Also my mac can t stay in sleep mode and wake up alone every hours

Thx Ventura !

I only started experiencing these WindowServer crashes on 13.0.1. Like the other reports, connecting to an external thunderbolt display seems to be a factor since I am not experiencing the issue using only my internal display or with an HDMI display on my MBP M1 16" (it has a HDMI port).

However, I CAN make it happen on command. When using my thunderbolt LG external display the WindowServer only crashes when I use the ⌘+tab shortcut to switch apps.

My laptop is crashing literally every half hour or so, regardless of whether I cmd+tab, fullscreen or not. Can’t downgrade either because my time machine broke just now as well. Apple please fix this!!

Just chipping in that I, too, am seeing this. Only with Command + Tab, and for me, it only started recently, like a couple of days ago. I am using 13.0.1; using MBP monitor along with external monitor connected via HDMI.

I have a 2018 15 inch with 2.2 i7 16 GB of ram and 1TB HD.

I started having htis issue about 3 weeks ago. Two OSs ago. It seemed to occur after updating my monitors to UHD samsungs. I went from running two external monitors at home and work via USBC HDMI cables to a single external UHD via USB C to HDMI. Always with the lid closed.

Apple wanted me to update to Ventura. I did. It helped. For about 3 days.

I seem to get the crash when the computer sleeps over night and when I am doing "stuff too fast."

I went back to the old set up with two 1080p monitors today. Same issue.

Today was me hitting spacebar to preview a document and then changing my mind and then changing my mind again - quickly.

Full screen isn't used frequently, if ever.

I am beyond frustrated. I am glad I found this forum as I was about to run out and buy a new machine thinking something hardware wise was failing. Seems a new machine will likely have the same issues. If I have to use the machine as a laptop without a monitor it is worthless.

I am at a loss at this point.