Cubase 11.0.10 Crashes after deleting tracks

Since the latest sub release 11.0.10 Cubase Pro feels extremely unstable after deleting tracks I don’t need in a project. The actual removal of tracks (could be empty audio tracks, or instrument tracks of various plugins like Battery 4, Zebra 2, whathaveyou) does not crash the program, but immediately afterwards when e.g. trying to opening the key editor on a track - gone. This happens very often. So much so that I already save the very moment I removed any track, since I’m expecting the program to crash. The crashed thread always looks the same:

0 libsystem_kernel.dylib 0x00007fff68c60e4e semaphore_timedwait_trap + 10
1 com.steinberg.cubase11 0x000000010a1fa232 0x10821d000 + 33411634
2 com.steinberg.cubase11 0x00000001095a5b91 0x10821d000 + 20482961
3 com.steinberg.cubase11 0x000000010a1f94b4 0x10821d000 + 33408180
4 libsystem_pthread.dylib 0x00007fff68d24109 _pthread_start + 148
5 libsystem_pthread.dylib 0x00007fff68d1fb8b thread_start + 15

which makes me think this is a bug in the current release. I’m working with templates, so there are obviously quite some tracks in there, but it never felt as unstable after removing tracks as it does now with 11.0.10. Is anybody else experiencing something similar?

macOS 10.15.7, 2019 Mac Pro


Could you provide the source *.crash, file, please?

Mac: macOS Console utility > User Reports folder or Crash Reports in macOS 10.15 (or ~user/Library/Logs/Diagnostic Reports).

Hello Martin,
Of Course. File attached. This is just one. I have of course more like this.

Cubase 11_2021-03-31-193935_Jorgs-Mac-Pro.crash (251.4 KB)


Reported to Steinberg. Thank you.

Thank you Martin!


Can you try to reproduce the crash without plug-ins, please?

Start Cubase in the Cubase Safe Start Mode [disable 3rd party plug-ins], please.

Martin, terribly sorry for the late reply to this. I got very busy the last months.
With the installation and use of Cubase Pro 11.0.30 Build 419 the issue seems to have vanished. I have yet to run into this issue again, even I this wasn’t listed as bug fix in the release notes.

So whatever might have helped here: I do not get these crashes anymore.


I’m glad it has been fixed.