Hi,
Cubase 9.5.10 tends to hang when closing a project, i need to kill it hard. The weird thing is, after starting C again and opening the same project, everything works normal again. My observation so far is that it does not depend on the project, just after the time I spent in the project, opening and immediately closing works fine, just after some time (more than a few minutes) it practically always hangs.
It is a brand new Windows 10 system, the problem didn’t appear on my old Win7 system with the same Cubase version. I have pretty much all the same plugins installed (some might actually be a bit newer than on the old system).
There is still some CPU usage, the screenshot show the sysinternals threads view when the hang happens:
Most interestingly is the State “Wait:Userrequest”, seems like Cubase is waiting for some input by me, but there is no window left but the main, and that is completely unresponsive.
Yeah, you’re right, most likely some plugin. I had another project now which didn’t show this behavior and I just tried and audio-only project with just using cubase channel strip, no problem. It is weird though that it only happens after some time. Or some action, that is.
The problem is now finding out which plugin is the culprit… I’ll try using listddls to find out which dlls are still loaded, but if anyone has a better idea, let’s hear…
As I still have this problem, I’m gonna bump this thread
By taking memory dumps in the deadlock state and looking at a threaddump in windbg, I’ve narrowed the problem down to the following plugins
Shattered Glass audio’s SGA1566 and Tonebooster’s plugins (the v3 ones, not the JUCE ones).
I think this is the thread where it somehow goes wrong:
*** WARNING: Unable to verify checksum for C:\Program Files\Vstplugins\ToneBoosters\TrackEssentials_v3\TB_Compressor_v3.dll
*** ERROR: Symbol file could not be found. Defaulted to export symbols for C:\Program Files\Vstplugins\ToneBoosters\TrackEssentials_v3\TB_Compressor_v3.dll -
1b 00000000`0014f650 00007ff9`09344c7a d2d1!RefCountedObject<D2DFactoryLocking<MultiThreadedTrait>,LockingRequired,DeleteOnZeroReference>::Release+0x39
1c 00000000`0014f680 00007ff9`33a31243 TB_Compressor_v3!VSTPluginMain+0x4390a
or other TB plugins.
I’ve opened a call at Tonebooster’s, Jeroen was very quick to answer, but sadly cannot reproduce the problem (well, I don’t know yet how to exactly reproduce it, except work for some longer time on a project with the mentioned plugins and then close it…)
I’ve opened calls at Steinberg, but so far all they did was put the blame on a third party plugin (the wrong one).
This problem happened so far with all updates of C9.5 and all revisions of TB plugins this year.
So Steinberg Support says that this is the fault of some Direct-X module, probably because it is old (the stack trace has some calls to Direct-X Libraries (d3d10warp.dll etc), Which seems kind of odd because Direct-X is a window system component and gets updated with windows updates, and I have the latest installed. But they’ve been wrong before…
Could anyone on a current Windows 10 please do me a favour and check for the following DLL versions in c:\windows\system32? (right-click “properties”, then go to details)
D3D10warp.dll - 10.0.17134.112 from 8th of June 2018
d3d11.dll - 10.0.17134.407 from 1st of November
d2d1.dll - 10.0.17134.407 from 1st of November
Most interestingly this behaviour does not happen at all in Reaper or Studio 1… I can use all those named plugins, and I never get any hang during a project close… and how fast those are!
This still happens even after installing a fresh new Windows 10 from a current Media Creation Tool with only Cubase 9.5.41, the specific plugins and the RME driver installed.
Is there really no one else having this kind of problem??? I cannot imagine that, i mean, my setup isn’t that special - an Intel 8700K system with Win10, a Fireface UFX, VST2 Plugins from Toneboosters (the V3 ones), Tokyo Dawn Labs (Slick EQ GE) and SGA.
But as soon as I add those VST plugins to a project and work on it for some time, when closing the project Cubase hangs and has to be killed…
It seems that no one here has the problem, which is still weird, but there might be a solution to this problem:
I’ve been in contact with a plugin developer and he provided me with a version of his plugin (one of those that caused the hang) compiled with VSTGUI 4.3 instead of 4.0, and with that version I never had the hang state so far.
The culprit is probably vstgui/lib/platform/win32/win32support.cpp, there is a commit that looks suspiciously related to the problem:
This seems to be related to DirectX, but a some questions remain:
Why do so few users encounter the problem on Win10?
Why is it only Cubase that has the problem but not Studio One or Reaper (which I tested here on my machine to see whether they show the same behavior)
Was there a change in Direct-X from Win7 to Win10. I never had the problem on Win7 which I used until February (on my old machine)
I also got the same problem… since today… i saw that when i open the task manager to end cubase there (as it doesn´t respond) that there´s
still a background process from cubase running that can´t be closed immediately. when i start cubase again it seems that the driver of my Steinberg UR22 has been killed by this also
I updated to Cubase 10 yesterday - (for now) the driver doesn´t get ´thrown out´ when i close it like with cubase 9.5.41 before, but i still have to close it in the task manager, as when i close it with ctrl + Q it closes the project, but cubase itself gives no response according to the task manager.
And this only happens when i work on the Project for a while - when i just open it and close it Cubase closes normally.
You still need that project?
I worked on the project again for about two hours yesterday, and cubase closed normally afterwards now. hmm… weired.
i´ll observe it the next few days and if it happens again i´ll get back to you. thanks for your advice in the meantime!
Sooo… i worked on different projects today and everything worked (almost) fine (except one more forced shutdown of Cubase), and now
suddenly the insert effects get transparent again… on all projects! so it´s not the project, but what could it be?
I´ll attach a screenshot, so you can see it Martin…
Can you please click to the “e” button of the plug-in? Does the plug-in GUI appears? How does it look like? Can you attach the screenshot with the opened plug.in window, please?
I tried to uninstall and reinstall interface driver, midi controller driver, some plugins - still the transparent insert effects. but then without
any obvious reason when i restarted it another time the insert effect colour appeared again. and today… it´s again gone (see screenshot).
when i load the plugins they look normal tough. i don´t know if there are other changes to cubase 10 as i didn´t work for long with these transparent insert effects.
is it possible to move this topic to another category - as it is no longer about cubase 9.5 hanging?
I just found out it might be connected with the waves plugin ´element 2´. i uninstalled it and afterwards cubase 10 didn´t have this
tansparent insert effects anymore - at least for now it doesn´t.
Interesting. The was a similar thread. The user said this happened with some freeware plug-ins. After uninstalling of these gate plug-ins the issue disappeared. Same as yours issue with Waves plug-ins.
If you open the Windows Task Manager, does it say something like “inactive” as the state for Cubase? If yes, it might be the same problem as I have, but you can only be really sure if you install windbg and have a look at the stack trace (which isn’t for the faint hearted).
Or you take a memory dump of Cubase when it hangs- For that you go into the Windows task manager, right click Cubase process and select “Create dump file”. Task Manager will tell you where the dump was written (usually “C:\Users\yourusername\AppData\Local\Temp\Cubase9.5.40.DMP”).
Put it someplace where I can download it and send me a link and I can probably tell you which plugin it is…
Do you use any of the plugins I mentioned above? It was a bug in earlier versions of the VSTGUI Framework some plugin developers use.
If you use Tonebooster plugins, get the latest version, they’ve fixed it (Thanks TB!).