[BUG] VST3 crash on Windows 10

[mourner]

@sdatkinson When loading NAM as a VST3 plugin on Windows 10, the plugin immediately crashes. At the same time, the standalone version runs well.

• OS: Windows 10
• Plugin version: v0.7.5
• VST3
• Studio One 6.2.1

Attaching the crash dump: Studio One_6_2_1_94935_Win x64_20230826_145409013.dmp.zip

Looks like some kind of null pointer exception but not sure how to debug this further:

EXCEPTION_RECORD:  (.exr -1) 
ExceptionAddress: 0000000000000000 
   ExceptionCode: c0000005 (Access violation) 
  ExceptionFlags: 00000000 
NumberParameters: 2 
   Parameter[0]: 0000000000000008 
   Parameter[1]: 0000000000000000 
Attempt to execute non-executable address 0000000000000000 

[mourner]

cc @olilarkin possibly iPlug-derived? I vaguely remember the stack trace consisting of some UI-related calls before it crashes... Anything I can do to help debug this?

(BTW, really looking forward to recording our new album with all-NAM guitars! But the plugin crashes on our guitarist's PC, no luck getting it to run yet 😅 Any pointers or workarounds highly appreciated!)

[mourner]

Update: Reaper managed to open the VST without issue on the same PC, so it must be something related to Studio One.

[sdatkinson]

Thanks for the dump!

I vaguely remember the stack trace consisting of some UI-related calls before it crashes

Ar you able to get that stack trace by any chance?

not sure how to debug this further

Are you handy enough to be able to build from source and run in a debugger? I have to admit I haven't done it on Windows myself yet, but the XCode project for macOS includes a definition for running the plugin in Reaper, which I've found really helpful for debugging issues related to execution inside a DAW; presumably something similar might be able to be done in Windows & Visual Studio...

Reaper managed to open the VST without issue on the same PC, so it must be something related to Studio One.

What I think happens is that Reaper has some pretty capable exception handling that keep it running smoothly; I'm not sure I'd conclude it's a problem with Studio One in the sense that I'm not yet convinced that S1 is doing anything that's not a valid use of the plugin API. If we're able to get more insight into this, it may be helpful for spotting something lurking that could be tightened up 🙂