Crash after crash on MacOS 13.2.1 M2
Hi all,
Hoping this is just the growing pains of a late model early adopter. I'm getting numerous crashes on a brand new M2, fresh copy of Max, different projects, almost nothing else installed on the machine, running on the built-in audio or an RME interface, with or without Rosetta. I'll attach some crash reports; I have a whole folder's worth that I'm collecting. I'm not an expert reading these, but it appears that it's the main thread going down every time. I'll admit that I'm not sure if this is a single problem or various problems depending on the project. Either way, Max is very far from stable on my machine and I'd love to get to the bottom of it.
Any help assessing the problem(s)
would be greatly appreciated.
I am having the same issue after updating to Mac OS 13.3.1. Have you had any luck resolving this issue?
Yes, still crashing with a particularly complex patch. No crashing with simple patches. It's probably my shoddy patching. Still, I can't seem to decipher what the problem is with these crash logs. I think I'm looking at randomly removing sections of the patch and seeing if it crashes as the only way to solve.
Did these issues remain for you both? I just got the mini m2pro with 13.2.1 and now refraining from updating to 13.4...
Same problem - regardless of patch complexity. In fact, some of the basic functions like option+right click on a simple object can make the program crash. I have M1 + Ventura 13.4. I wrote to Cycling74 support. Will let you know
This might be a weird reply.
I have had Ventura on M1 since early beta release (because my developer license).
Very very oddly, whenever Apple pushes a beta Update, and before I install it, Max starts crashing - right at the moment the update is available.
This has been happening intermittently over the past year.
Whenever I install the newest beta, everything begins working fine again.
Although, and maybe do to my work, I have had to trash the Max preferences a few times after super hard crashes,
All said, I am on Venture 13.5 ( I think beta 4) and everything is working perfectly.
Advice when in new territory , and against what everyone else says, install the most current update.
On a positive note about crashing, this has caused me to put a whole lot more presets and loadmess than I usually do during my build and test phases. So there's that.
2 cents.
~wil
Returning to this to close the circle on my issue. Turns out I was abusing a couple of panel objects by changing their bgcolor very rapidly. By itself, it wasn't problematic. However, after deleting almost every other function in my large patch, my constantly crashing only stopped after removing the panel objects. I suspect that there was a bottleneck linked to screen redrawing that was somehow exasperated by the audio processing or control data in my patch. Who knows? At the end of the day, the crashing stopped when I removed the panel objects, crashing that was occurring on an M2 computer that wasn't happening on an Intel machine.
Having same issue on Windows 11. Is there a good solution to creating a color panel which doesn't crash?
000masa000, I replaced [panel] with [jit.pwindow]. That has been working well.