Exported VST causing Access Violations

[Adam_G]

guys i have a vst that is crashing in every daw i use it in. im assuming this is related to my project specifically but has anyone seen this error?

[d.healey]

@Adam_G never seen that. Does it happen with a minimal project?

[Adam_G]

@d-healey no it doesnt. in the error "myVST" is the name of the vst by the way

[d.healey]

@Adam_G might be related to your audio settings

[Adam_G]

@d-healey im afraid this isnt it as its happening across multiple machines with different audio settings. i was sure it was related to my project but i have whittled it down to only elements that i have successfully used before and its still occurring. does that point to hise? i guess not if noone else has seen this behavior in their plugins :(

[Adam_G]

got this info from the crash report with Logic

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       KERN_INVALID_ADDRESS at 0x0000000000000034
Exception Note:        EXC_CORPSE_NOTIFY

Termination Signal:    Segmentation fault: 11
Termination Reason:    Namespace SIGNAL, Code 0xb
Terminating Process:   exc handler [7985]

"Termination Signal: Segmentation fault: 11" does this mean its related to Xcode? I compiled with 14.3

[Christoph Hart]

@Adam_G you have to run the debug build to find out whats happening, these crash reports don‘t contain any information.

Go into Xcode and select build for testing, then load the plugin with the Debug postfix.

[Adam_G]

@Christoph-Hart once I compile the debug version of Hise, do I just export the vst normally from it? how do I load the plugin with the Debug postfix?

[d.healey]

Does this only happen when compiled as a plugin not as a standalone?

[Adam_G]

@d-healey haven't tried standalone yet, ill test that now.

[d.healey]

@Adam_G Everything's easier to debug in standalone so if you get the problem there it will help

[Adam_G]

@d-healey no crashes on windows standalone. my Mac vm is very slow so its still currently exporting but I think this may be the same issue. my project too uses the midi overlay panel https://forum.hise.audio/topic/4656/midi-overlay-panels-in-compiled-plugin-crashing-daws/22?_=1684334539180

[Adam_G]

@Adam_G said in Exported VST causing Access Violations:

@d-healey no crashes on windows standalone. my Mac vm is very slow so its still currently exporting but I think this may be the same issue. my project too uses the midi overlay panel https://forum.hise.audio/topic/4656/midi-overlay-panels-in-compiled-plugin-crashing-daws/22?_=1684334539180

nope still crashing on Mac even after implementing this. no problems in standalone but it only happens when I close and reload the plugin. I'm unclear how to use the debug version once its compiled though

[d.healey]

@Adam_G Run it from within xcode. There should be a way to attach it (xcode's debugger) to a DAW instance (I'm not familiar enough with xcode, there is probably a YouTube video for it).

[Adam_G]

@d-healey I think you're the only one who makes YouTube videos on hise

[d.healey]

@Adam_G But I'm not the only one who makes videos about debugging with xcode :)

[Adam_G]

@d-healey i found one other one! xD ( big thanks to @Dan-Korneff )

now my mac virtual machine is apparently too slow to build the debug version in xcode without getting out of memory errors smh.

can i get the same info from doing this process on windows? that question is mostly for @Christoph-Hart

[d.healey]

@Adam_G I think you can avoid the memory issue if you reduce the number of compile threads (don't ask me how)

[Adam_G]

This post is deleted!

[Adam_G]

@d-healey

defaults write com.apple.Xcode PBXNumberOfParallelBuildSubtasks 8

in terminal to reduce compile threads