VM Region Info: 0x388 is not in any region. Bytes before following region: 140737487367288
REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL
UNUSED SPACE AT START
—>
VM_ALLOCATE 7ffffff0f000-7ffffff10000 [ 4K] r-x/r-x SM=ALI
ID Vend/Dev
bac4 67ef1002
Seconds Ago ID Type
1100000.0 bac4 Attach
I have been running into the same issue forever. We’re an architecture firm and had a Mac mini M1 constantly crashing. I thought it was reaching the max memory bandwidth and with other apps open simultaneously (AutoCAD, email, calendar, safari, etc), things hit a limit and SketchUp would just quit.
So we bought a Mac Studio with an M1 Max and 32gb ram (which has 4x the memory bandwidth of the mini). Still crashing.
If I open the same model on my iMac Pro (2017 intel-based with 64gb ram), I can have the same model open for days without quitting, and never see any crashes.
Seems like SketchUp has not been perfectly optimized for Apple Silicon, and while it did run OK using Rosetta, and still sometimes OK in SU22 which SHOULD be optimized for Apple Silicon, the developers have not yet tested against these DAILY crashes.
If anyone at Trimble/SketchUp monitors these forums, please escalate this to the very top. Your app is absolutely debilitating on modern Macs which are supposed to handle your application so much better than my 5+ year old intel Mac. What’s going on?!
Ventura. Your crash logs are running Ventura (mac os 13)
Sketchup 2022 is (still) not listed as compatible with Ventura. They tried it on their macs, it worked, but no stamp of approval.
There are a handful of similar threads on this forum, and the main solution is to rollback to monterrey.
Sketchup is fully optimized with Apple Silicon, it was actually rewritten specially for Silicon. The issue at hand is the difference of rhythm, Mac os beign released in oct/nov while sketchup tends to be released in jan/feb.
Although you’ll find a handful of similar cases here, you’ll also find that many people have made the update without any trouble, including sketchup staff. So it’s not completely clear what is making SU22 crash on some M1/M2 macs.
… I don’t see what the gimp toolkit has to do in this…
No, I’d say it is because the dev teams are focused on SU23 and don’t want to spend time answering helpdesk tickets and fixing issues with a version about to be replaced.
If Trimble officially announced that SU22 is compatible with Ventura, they would have to provide fixes to the handful of situation that makes it crash.
Or they can simply NOT endorse Ventura for 22 and answer “well yeah, try it at your own risk”.
edit : I spent 3 years sharing a flat with a dev, and yeah, they’ll do that. no need to divert ressources to fix an issue in an old version if you’re about to release a new - and fixed - one
unless you have a massive team of devs of course, like adobe, releasing fixes and updates every week or so
Yeah but the crashing on the M1 mini started on Monterey too, so it’s got nothing to do with SU22 and Ventura. In fact I was eager to update to Ventura to see if that would solve the issue, but it didn’t.
And SU22 works BEAUTIFULLY on Ventura on my iMac Pro, never ever crashes.
I don’t think SU was re-written for Apple Silicon. Without doing a thing, SU would be emulated via Rosetta 2 on the fly on Apple Silicon. Starting with SU22, Trimble added the Apple Silicon build target and might have needed to add or adapt some code, but it definitely was not re-written for M1/M2.
So while it may run OK, it does not feel fully optimized and the crash logs indicate memory handling errors. I do hope they spent a decent amount of time running M1 and M2 computers with SU22 over the past many months and have addressed these issues in SU23.
I get the annual release cycle, but SU is debilitating on M1/M2. SU22 should have received some intermediate update to remedy in the meantime.
Silence from Trimble on the matter is not encouraging. They could ease the pain by announcing a product roadmap or at least acknowledge the issue has been addressed for a future version/update.
