Just ran into this issue and so far have isolated it to JUCE versions 8.0.8 and later, so I’m assuming whatever changed was in that version. I don’t see any breaking changes so not even sure where to begin, and no exceptions are thrown when debugging.
To clarify, the plugin windows still animate and respond to being moused over, but they can’t be clicked on and neither can anything else in the DAW, forcing me to force quit. This happens the same in REAPER and Ableton so far and only on windows, leading me to think it’s a Direct2D issue since I see a bunch of tweaks were added to that renderer in 8.0.8. Also of note is that it doesn’t happen with the blank template plugin UI, but it’s hard to know where the cause may be since debugging doesn’t cause any real red flags.
Any leads would be appreciated!
I assume you’ve tried the latest version of the develop branch?
To isolate the exact commit could you try git bisect?
I’m unsure if you’re saying that a JUCE host or a JUCE plugin is the issue?
Are you able to reproduce the issue using any of the provided examples in the JUCE repo?
FWIW I had an host freezing issue with Juce 8 that happened to be a global static juce::Image. Removing it fixed it.
1 Like
I haven’t been able to try isolating it further yet but will once our new product launch is over. For now I’ve just downgraded to 8.0.7.
And yeah to clarify it is a JUCE plugin that is the issue. VST3 and AAX on Windows both present the problem (VST3 in every DAW I tried).
I’ve checked for any static objects and there were none on the UI end, some static class member functions but inlining all of them didn’t change anything.
Will report back once I can nail down where the problem lies!
2 Likes
I’ve been getting reports like this from users (windows only, clearly D2D related).
I haven’t been able to reproduce it yet though, so I’m curious to see where this ends up.
