You can make a difference in the Apple Support Community!
When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.
When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.
Sonoma keeps crashing frequently and randomly. Never had any such issue with Ventura. Issues started after installing Sonoma on my Mac Book Pro (Apple M1 Max, 16 inch). Clearly a buggy OS, all apps up to date. Don't point at apps, please ...it's a Sonoma problem.
[Re-Titled by Moderator]
My MacBook M2 (Pro 13" 2022 release) has crashed once a day since the update to MacOS Sonoma, it's surprising that there hasn't been a patch update to fix this problem considering the amount of people that are vocalizing their concerns.
Usually upon opening the lid for the first time after having my computer on the charger overnight, I am prompted to re-enter my password, which tells me that it has been restarted. After logging in, I am greeted with a message stating that _windowserver has crashed, and I can submit a report to Apple or ignore.
This absolutely is not a hardware or application issue as I have had this computer since its release last year, and haven't begun to experience problems until this update.
This is ridiculous, if I could regress back to MacOS Ventura I would do it in a heartbeat.
Hi all - I've been one of the people experiencing this problem, and it seems to have gone away now. Since my crash report always started with a message about a network issue, I had a hard look at my network settings, and realized that I had a third-party driver installed for a USB-C hub with an ethernet port. I removed that driver; experienced at least one more crash; but thereafter it's been stable. So, that's something to look at for some of you. It seems clear that not everyone experiences this problem in the same way, so I don't imagine it'll be a solve for everyone.
(And I weigh in agnostic on how much responsibility Apple/Sonoma has for this issue... Perhaps they changed the way that drivers work in the OS such that different kinds of drivers are now experiencing this very similar intermittent crash... Or perhaps there are a series of unrelated errors from driver developers that are only now coming to light... Can't really assign blame from the outside. But I do hope someone from Apple is having a good look at these reports.)
Fascinating. I have not cleared the cache, but have not had more crashes in recent days. Might the cache have gotten cleared by the app or system?
Has anyone else has the crashes become less routine?
response to TRS80child...
Yes I may have found my issue. I've been using CalDigit's Element Hub successfully for the past two years. It's the only Hub that wasn't glitchy with the new M1 chipset. I disconnected it and that solved the problem. I'm not convinced however that's the only issue. I went ahead and plugged it back in without any components - no crash. So I've been adding back USB-C devises still no crash. It may be my original configuration which is extensive. Including daisy chaining the Hub. Talking to CalCigit - the hub should be able to handle daisy chain without issue. I'll continue to add items till I get back the crash. I'm guessing it's not the USB-C components but rather the USB-A (3.0) on the Hub. I'll find out. My suggestion to others is unplug everything from the USB-C ports on the MAC and see if it still crashes, then add back items and go from there. Good luck.
Plus according to most of crash reports deals with Intel only programs! One user had 71 Intel only pieces of software installed! To me that is just a little over the d]edge iMHO! Plus 7 interfaces including an iPhone connection is just a little too much for processors to handle!
I've been thinking to run a script like yours, but for
ps -ax -o "rss,wq,command" 164
Process 164, at present, is loginwindow, which has been suddenly exploding in memory size, from ~25mb to 10GB. I tracked down a cache belonging to it, nuked it (which caused it to crash on logout, providing me with more useful information). I suspect that the use of a specific app is causing the memory bloat.
In your case, I suggest installing iStat Menus and keeping an eye on the memory in your menu bar. Then you'll be able to see which process is exploding. For instance, I found a serious bug in Final Cut Pro where, after a micro SD card has been inserted, FCP will start filling up memory until the computer crashes, pretty much. I can't help wondering if something like that is happening on your computer.
The number 164 is, of course, circumstancial, so if you want to do this and not have to figure out which number loginwindow happens to be, in each case, you might try instead:
ps -ax -o "rss,wq,command" | grep loginwindow
I've never used the new screen saver, and was just about to write that and report it not having crashed recently.
HA!
Just found a crash during sleep again.
panic(cpu 0 caller 0xfffffe001b40e6cc): "skr.umd.upipe:551:IDSClientChannelNexusOS": skr 0x0xfffffe29b3d7d400 sg 0x0xfffffe1b49807348 (idx 14) unable to satisfy mandatory allocation
BTW, there is a thread with that topic In Reddit.
https://www.reddit.com/r/MacOS/comments/16w4uit/panics_in_sonoma/
I have lost my sound since updating. It will come and go when I try different things, but it is temporary. I have a cleanup app installed on my computer, but it has been there since December and these issues just began. Not sure what to do, but if it is from the update I sure hope they fix it soon.
Regarding CalDigit Element Hub as potential issue. I've found a way to stop the crashing but clearly this is a OS issue. It just shouldn't happen. It appears if I add more than 5 devices to CalDigit (monitor, hard drive, ethernet, so on) the system crashed. I've been adding back devices one by one to find out if one particular device is the issue - but I'm convinced this is an OS issue not CalDigit. I'm going to contact CalDigit as a head up. I hope Apple sends an update soon. Fixing the the problem is taking more time than it's worth...
Amys6: I've been on the phone with Apple care three times. My 2021 M1 Max had no issues until I installed Sonoma three week ago. With Sonoma it crashed routinely until I unplugged my CalDigit hub and all connections. I was able to determine the issue may be connecting my monitor through the hub using Apple's HDMI to USB-C. Now I'm able to run everything else (except my monitor) through the Hub with no issue. I agree with one user that it appears to happen when the computer sleeps and then turns on. Anyway back to Apple Care. They don't have any records of these crashes and stated that new software with crashes could be due to a number of issues. Bottom line don't expect a patch soon. Not happy paid for apple care - really doesn't give me anything.... Still doing my own plug and check routine. I'll try turning off sleep next and see it that works.
Wow, that's interesting been using Apple's HDMI to USB-C for years. Have a 12-year-old Apple Studio monitor that has always been just fine. Sonama has been just a disaster. It does seem to happen when I lose my cursor going between the computer screen and the monitor.
I think Sonoma is the worst macOS I've seen as Apple developers are trying to make macOS look and feel more like iOS which I hate. Mojave is one of the best macOS until Apple started making it look more like iOS.
I used the apple support chat (for the first time) and my pleasant contact was not aware of the problem. Only suggestions were safe mode, reinstall Sonoma or wipe the machine and install Ventura. They promised to report the problem. I referenced this discussion and the larger Reddit thread.
it wouldn’t hurt to have everyone here do the same.
For what specifically? It seems people here have multiple problems, and with insufficient information, there's nothing we can do but wait for Apple to work on all the crash logs and feedback they've received, and rectify any bugs they created.
Likewise the makers of any software that doesn't work properly with Sonoma.
FYI:
My many crashes were all with dynamic wallpaper off. Upon installation, I quickly reverted to my old lovely still of the Minnesota canoe wilderness.
Another crash last night - bright pink screen while reading some boring Safari site, then POOF!
I just submitted the bug report, as suggested, and have cleared the Safari cache.
MacBook Pro with macOS Sonoma crashes frequently and randomly.
