Cubase 9.5 hangs on project close on Win 10

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:
https://github.com/steinbergmedia/vstgui/commit/55d14da4fce3987e0d73d739142ddee207bd6b34#diff-ecdabc5d3e340ff6cb2a761a68ba51ef
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)

Same problem here.
Cubase 9.5 hangs on Windows 10 when closing project. I have same ver. on OSX and is OK.

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

Hi,

Could you attach an affected project, please?

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?

Would be nice to have an option to try.

If you would know, what steps to do to evoke the situation while quit, that would be great.

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…
https://www.dropbox.com/s/5swfw5f8d5lvj6r/Screenshot%20-%20Transparent%20Insert%20Effects.png?dl=0

Hi,

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?
https://www.dropbox.com/s/x61jt564q4dh9nh/Screenshot%20-%20Transparent%20Insert%20Effects%202.png?dl=0

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!).

Hi there, I’ve the same issue but I’m on a mac with macOS Sierra. I don’t have issues if I work on projects with only audio files. If I start to use Spitfire Audio libraries the issue rises. And like in your case if I attempt to close the project after a few minutes it closes well. If I try to work for more time the project hangs by closing.
For sure we are using different plugins, we are on different OS systems with different libraries. The only stuff we are sharing is Steinberg’s software. The common sense let me suppose hat the issue is not in our projects or computers but by Steinberg. I mean, maybe…
But I really don’t know how to find a way to fix this.

In the end it way actually some plugins (several from different vendors which made it hard to find…) that were the culprit. Some of those bugs were fixed, one other that didn’t get fixed I just didn’t use anymore until I tested it again a few weeks ago with Cubase 10.5 and suddenly no problem anymore, no deadlocks.

Similar thing happened when sonible release their smart:comp, there were actually several users on gearslutz who had the “Cubase hang” problem with it, and the developers had a hard time finding the bug. Very esoteric.
Cubase seems to handle plugin/dll unloading differently than other DAWs. I’ve never heard it happen on MacOS, though.

Hi fese. Did you ever get to the bottom of this? I’m here in Feb 2021 after dealing with what seems the same for over a year. It happens with Acustica Audio plugins in my case. There are a number of reports of it, had numerous tickets opened. Support found the D3D10Warp.dll problem and once more we seem to be at a dead end.

Could the solution be adding this…?

Please /RELEASE me…?

Hi garethk,

in the end, it was the plugin developers that fixed it. Here is one excerpt from the one that eventually found the problem (at least in the VSTGUI Framework the he used for his plugins.)

It seems something changed in DirectX (D2D). It probably changed in a Windows 10 update (the first versions of Windows 10 were not affected by this).
Hopefully, those who use VSTGUI may have the possibility to fix the problem.
As far as they do not depend on an earlier version of VSTGUI (<4.3), they can update to 4.3.
Those who do not use VSTGUI (or those who would like to know more about this issue) should check a diff between VSTGUI 4.2 (or 4.0) and VSTGUI 4.3.
The following file, especially… and its ~D2DFactory destructor in particular (+ the “useCount” usage in v4.3):
/lib\platform\win32\win32support.cpp/
If one uses VSTGUI, it should then be worth starting by debugging this destructor.

Most other Plugins use the framework JUCE, and I have no information about that. Even more confusingly, another JUCE-based plugin that showed the hang problem seemed to have “fixed” itself after a couple of months or so after not using it. I only noticed that because the dev sent me a bugfix to test, and I compared the old and new versions and I could not reproduce the hang anymore.

1 Like