# Juce crashes with vst3 "The Sauce"

**URL:** <https://forum.juce.com/t/juce-crashes-with-vst3-the-sauce/53092>\
**Category:** General JUCE discussion\
**Created:** [September 20, 2022, 6:37pm UTC](https://forum.juce.com/t/juce-crashes-with-vst3-the-sauce/53092 "2022-09-20T18:37:43Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![ACEric](https://avatars.discourse-cdn.com/v4/letter/a/919ad9/32.png) [@ACEric](https://forum.juce.com/u/ACEric)\
**Post date:** [September 20, 2022, 6:37pm UTC](https://forum.juce.com/t/juce-crashes-with-vst3-the-sauce/53092/1 "2022-09-20T18:37:43Z")

</div>

Juce pluginhost 6 and 7 both crash immediately when attempting to show gui of vst3 plugin “The Sauce”.  
Daw which uses juce, does the same thing.  
Tested in non-juce daws, they load the plugin normally.

---

<div class="post-metadata">

**Author:** ![reuk](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/reuk/32/21494_2.png) [@reuk](https://forum.juce.com/u/reuk)\
**Post date:** [September 20, 2022, 7:21pm UTC](https://forum.juce.com/t/juce-crashes-with-vst3-the-sauce/53092/2 "2022-09-20T19:21:23Z")

</div>

On which OS is this a problem?

---

<div class="post-metadata">

**Author:** ![ACEric](https://avatars.discourse-cdn.com/v4/letter/a/919ad9/32.png) [@ACEric](https://forum.juce.com/u/ACEric)\
**Post date:** [September 20, 2022, 8:52pm UTC](https://forum.juce.com/t/juce-crashes-with-vst3-the-sauce/53092/3 "2022-09-20T20:52:29Z")

</div>

Windows 10, 11

---

<div class="post-metadata">

**Author:** ![reuk](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/reuk/32/21494_2.png) [@reuk](https://forum.juce.com/u/reuk)\
**Post date:** [September 21, 2022, 1:15pm UTC](https://forum.juce.com/t/juce-crashes-with-vst3-the-sauce/53092/4 "2022-09-21T13:15:49Z")

</div>

Before showing the window, the AudioPluginHost calls `hasEditor` to check whether the plug-in has an editor to display. For VST3 plug-ins, the only way to know whether the plug-in has an editor is to actually create the editor, and then to check whether this operation succeeded.

It looks like the crash happens when destroying this short-lived editor. The actual crash happens inside the plug-in, so I believe the issue is in the plug-in code, rather than in the hosting code.

I’d recommend filing a bug report with the manufacturer of this plug-in.

---

<div class="post-metadata">

**Author:** ![ACEric](https://avatars.discourse-cdn.com/v4/letter/a/919ad9/32.png) [@ACEric](https://forum.juce.com/u/ACEric)\
**Post date:** [September 21, 2022, 1:51pm UTC](https://forum.juce.com/t/juce-crashes-with-vst3-the-sauce/53092/5 "2022-09-21T13:51:41Z")

</div>

If the fault is with the plugin, then why do all the non-juce daws, load this plugin normally?  
In that case, what are the non-juce daws doing that seems to bypass whatever issue is causing the crash?

---

<div class="post-metadata">

**Author:** ![reuk](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/reuk/32/21494_2.png) [@reuk](https://forum.juce.com/u/reuk)\
**Post date:** [September 21, 2022, 2:01pm UTC](https://forum.juce.com/t/juce-crashes-with-vst3-the-sauce/53092/6 "2022-09-21T14:01:25Z")

</div>

I guess those DAWs are not creating and then immediately destroying the plug-in editor, but a well-behaved plug-in _should_ be able to handle this situation.

If I avoid destroying the editor, then I can get JUCE to open and display it. I think this indicates that the problem is in the editor’s destructor. Removing the destructor call isn’t a good fix in general, though, because it will lead to resource leaks.

---

<div class="post-metadata">

**Author:** ![ACEric](https://avatars.discourse-cdn.com/v4/letter/a/919ad9/32.png) [@ACEric](https://forum.juce.com/u/ACEric)\
**Post date:** [September 21, 2022, 2:40pm UTC](https://forum.juce.com/t/juce-crashes-with-vst3-the-sauce/53092/7 "2022-09-21T14:40:12Z")

</div>

So what can be done about it?

---

<div class="post-metadata">

**Author:** ![reuk](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/reuk/32/21494_2.png) [@reuk](https://forum.juce.com/u/reuk)\
**Post date:** [September 21, 2022, 2:44pm UTC](https://forum.juce.com/t/juce-crashes-with-vst3-the-sauce/53092/8 "2022-09-21T14:44:01Z")

</div>

File a bug report with the plug-in developer, and hopefully they’ll fix the bug.

---

<div class="post-metadata">

**Author:** ![ACEric](https://avatars.discourse-cdn.com/v4/letter/a/919ad9/32.png) [@ACEric](https://forum.juce.com/u/ACEric)\
**Post date:** [September 21, 2022, 2:53pm UTC](https://forum.juce.com/t/juce-crashes-with-vst3-the-sauce/53092/9 "2022-09-21T14:53:20Z")

</div>

I have now filed a report.

---

<div class="post-metadata">

**Author:** ![reuk](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/reuk/32/21494_2.png) [@reuk](https://forum.juce.com/u/reuk)\
**Post date:** [September 21, 2022, 4:17pm UTC](https://forum.juce.com/t/juce-crashes-with-vst3-the-sauce/53092/10 "2022-09-21T16:17:20Z")

</div>

I’ve also reported the issue, and included a link to this thread. I’ll post an update if I hear anything back.
