I have had a couple of instances of Cubase crashing when it’s been left idle. Typically this happens if I leave it on, with a session loaded, overnight. It’s not a huge issue, since I save often and Cubase creates backups. Still, I’d like to understand what’s causing it… If it’s a plugin, I’d like to remove/replace it from my tools. If it’s a memory overflow, I’d like to at least report it to Apple. I have 64 GBs of RAM so this could explain why it takes 12-20ish hours. I’m running a Mac Studio M1 Max.
I tried looking at the logs, but they’re extensive and I’m not familiar enough with them to be effective. I could only discern that it’s Thread 56 (this time) that crashed.
Attached is a copy of the logs. If anyone can tell me who/what is to blame I’d be most grateful
I think I know what the crash is, but I have no idea what to do about it.
AI thinks:
Ouch. Seeing a SIGABRT (Signal Abort) is basically the software equivalent of a program throwing its hands up and quitting because it detected an internal inconsistency it couldn’t recover from.
Unlike a crash caused by an external error, a SIGABRT is usually self-inflicted—the program (or a library it uses) called the abort() function because something went very wrong.
AI is never wrong is it? it just have the wrong starting point I guess this would make sense that if Cubase is trying to access something while the mac is saving power or something it could cause a crash.. ofcourse always send crash dumps to Steinberg.
I guess I was hoping to find something soon, preferably before a recording session with 2 singers this Saturday. That’s why I asked if anyone here could decipher it.
didn’t this just happen overnight? you cant be bothered to close Cubase at the end of the day and start it again the next day? if it crashes after 12 hours.. just restart after 8 and you should be good to go
If something is crashing Cubase, I’d rather remove and replace it from the workflow and/or fix it. I’ve seen numerous examples of logs being looked at and a faulty plugin being identified. I guess I just hoped that would be the case here.
which os are you running on? I have upgraded to macos 26.3 now. I left my cubase on for some hours. when I came back Cubase crashed and my thunderbolt clearly lost connection and restarted. did not happen on 15.7.
It happens to me on Sequoia. Is your crash report after reopening always empty?
For me it was sometimes due to T-Racks 6 plugins (sometimes no info at all). Even if those were disabled. Since I removed all of them from the latest sessions, this is not happening anymore.
I’m on 26.3 now. I updated to Tahoe from Sonoma in February. It happened before as well. I cannot recall for certain if it happened with Cubase 14, but it does with 15
I haven’t been paying attention to the crash reports because of the project being saved and Cubase being idle. So I would just move on. This last time was ‘one time too many’ so I decided to start looking for a source.
Your T-Racks situation is notable though. We have a skit in the middle of a track we’re working on and I randomly threw in an IK hall reverb (can’t recall what it was called) on a short vocal I want “far away” in the skit. I’d never used that plugin before (got it from the group buy). That project was loaded during the last crash. If I’m remembering correctly, this would be the first time on Tahoe and with an IK plugin that the crash happened. Food for thought. I’ll have to take a closer look when I’m back in my studio later. Thanks for replying.
I guess this would make sense that if Cubase is trying to access something while the mac is saving power or something it could cause a crash.. ofcourse always send crash dumps to Steinberg.