Helix Native 1.91 Crashing

GP Crashes whenever I save a preset inside Helix Native 1.91 (Windows 10 x64). I’ve used two other VST hosts that do not have this issue. Any ideas?

thanks,
mark

What version of Gig Performer?
Do you have a crash report?
Did this ever work?
Have you performed a Windows update recently?

  • I am running GP 3.7.0
  • I’ve Sent the crash report to GP, If you let me know where it’s stored I can upload it.
  • Today was the first time I’ve tried to save Helix presets inside GP, so no it’s never worked.
  • Yes, I’ve run updates and I am running Windows 10 Pro 1909

thanks,
mark

Thank you for your crash reports. This is definitely a crash in Helix itself and it has nothing to do with GP.
Here is the information

<ExceptionAddress>0x23edffb81eb</ExceptionAddress>
<ExceptionModule>C:\Program Files\Common Files\VST3\Line 6\Helix Native (x64).vst3</ExceptionModule>
<ExceptionModuleBase>0x23edf9e0000</ExceptionModuleBase>
<ExceptionModuleVersion>1.91.0.0</ExceptionModuleVersion>

If you contact Helix 6 developers and provide them with this data as well as steps to reproduce - they will most likely be thankful and able to fix the problem quickly.

Cheers

Thanks for the info.

I’ve opened a ticket with Line 6. However, that plugin works properly in two other VST hosts on my same machine.

-mark

If a plugin crashes - it crashes inside the plugin’s code. The host cannot really crash the plugin code. This means that the bug is inside the plugin.

Also note that you used VST3 version of these plugins. When you are making comparisons - please make sure that you also use VST3 and not the VST2 version of the plugins in other hosts.

Doesn’t matter — some hosts use more parts of the plugin API than others — and if the developer only tests a few hosts, they may not find any issues.

Okay It crashes when the plug-in invokes its pop-up dialogs. These are standard windows UI dialogs not contained within the plugin window (see image captured using Bluecat’s Patchwork). The crash happens whenever the plugin trys to display one (changing global settings or saving presets).

I’m confused - what does Bluecat Patchwork have to do with this?

It was probably used as a wrapper within GP to show where the dialog window was crashing Helix (and subsequently, GP) when NOT using the Patchwork wrapper.

Sounds like Helix is trying to invoke UI stuff without using the main GUI thread. Definitely a Helix bug.

Blue Cat’s Patchwork is a VST plugin, but also a standalone VST host. I was using the host version to show the dialog.

Note: If I host Helix inside Blue Cat’s Patchwork inside Gig Performer it crashes.

Also, Windows message boxes do not have to be called from the UI Thread. But they may be trying to set the owner HWND.

I see that someone else responded to your post on the line6 forums reporting exactly the same problem with Cubase.

Thanks for the followup, I filed a ticket a few days ago and after some back and forth here’s the latest response from Line6…

Thanks for providing, Mark. From what I’ve traced this is a known GUI issue in Native, when using third party VST shells. I suggest only using the VST2 version, but I’m going to forward this to our QA team so they can review.

Note: The VST2 also fails…

OK - hopefully you responded to them that the VST2 version also fails? With respect to third party VST shells, to what are they referring? If you’re running Gig Performer, why should their system care about third party shells…what am I missing?