Exported VST causing Access Violations

[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

[Adam_G]

@d-healey still seems to be hanging on 299 of 302 steps :(

[Christoph Hart]

can i get the same info from doing this process on windows?

Sure, if it also crashes on Windows, you can debug it there, no need to run a VM.

[Adam_G]

@Christoph-Hart thanks Christoph :)

[d.healey]

@Adam_G said in Exported VST causing Access Violations:

@d-healey still seems to be hanging on 299 of 302 steps :(

How long did you wait?

[Adam_G]

@d-healey its still running right now

[d.healey]

@Adam_G Yeah that's not right

[Adam_G]

@d-healey i shut it down, but now im struggling to complete the process in visual studio as the instructions are for xcode. i can compile the .vcxproj but i cant see where to set the daw to open it with

[Christoph Hart]

@Adam_G VS Menu -> Project -> Properties (last item) -> Debugging -> Command -> Browse.

[Adam_G]

@Christoph-Hart thank you! on windows vsts dont compile directly to the vst folder. do i need to set that for my working directory ? im using Reaper and the vst isnt showing up when i start debugging

[Adam_G]

anybody out there familiar with debugging in visual studio?

[d.healey]

This should get you started (it's what I used)

[Adam_G]

@d-healey thank you very much

[Adam_G]

i think i managed to make it work thanks to everyones help. no crash in reaper but i replicated it in FL studio. is this what im after?

Exception thrown at 0x00007FFD4CA49F35 (myVST.vst3) in FL64.exe: 0xC0000005: Access violation reading location 0xFFFFFFFFFFFFFFFF.

[Christoph Hart]

@Adam_G No it seems that you're still using the release build in FL Studio - it should break in MSVS with the exact line that causes the crash. Make sure you load the correct plugin version (it should have a Debug postfix).

[Adam_G]

@Christoph-Hart hmm i compiled the vst with the debug version of hise standalone. i must be missing a step, ill try again

[Christoph Hart]

@Adam_G no you must compile the plugin as debug build from within VS. Open the solution you‘ve creates after exporting from HISE, then switch the configuration to Debug and build.