Cubase Crash using the Range tool

Hi, I would like to report a bug for Cubase Artist 14.0.20 and I thought there was a process to follow in this forum. but I can’t find it. So I’ll describe it here.

The bug is related to trying delete one or more bars in the timeline view. When I am in the timeline view I use the Range tool with CTRL-SHIFT to select all the tracks for the one or more bars that I want to delete. But when I go to the Edit menu Cubase crashes. My intention is to go Edit > Range > Delete Time, but I can’t because CB crashes before I can select it. I can do SHIFT - Backspace successfully, but as soon as I go to the Edit menu with the range still selected Cubase crashes.

I have had it work before but today every time I try, it’s the same thing. It also get the same behavior in different projects.

As well, after the crash and I restart CB I get the usual pop-up and I send the crash report to Steinberg.

I am using Cubase Artist 14.0.2 on Windows 11 24H2 with 16GB RAM AMD Ryzen 5 and 1TB SSD.

Thanks
Peter G

K I just tested again. I think the problem is with the Arranger track. If I remove it, it works as expected and deletes the selected bars. If I add the Arranger track back without any events, CB crashes as described above.

I tried to reproduce it but I experience no crash. Things work as expected on my system.
Can you please go to your Documents folder, there Steinberg → Crash Dumps.
Look for Cubase crash dump files of the recent crashes. The name of each file has a date and time info in it - year.month.day time.

Kindly post one or two in this topic.

Here are some of crash dumps…thanks.
Cubase 14.0.20 64bit2025.4.16 19.49.01.475.dmp (1.5 MB)
Cubase 14.0.20 64bit2025.4.16 19.52.27.798.dmp (1.5 MB)
Cubase 14.0.20 64bit2025.4.16 19.55.22.578.dmp (1.5 MB)

1 Like

Thanks. All three files point to the same crash.
It also looks rather familiar.

We have to wait until after Easter before anybody from Steinberg can look at it.

Thanks for the quick response. I appreciate you taking the time to look at it.

Reported to Steinberg. Thank you.

So i just installed 14.0.30 and tested out the issues i described above and it appears to be fixed. Thanks.

1 Like