zyn fusion crashes reaper in windows 10

[rexendevar]

i've tried v3.0.5 and v3.0.1 of zyn fusion. Both of them crash Reaper (v6.0.4) when the plugin is opened. I assume it's something to do with the GUI because it only ever crashes just after loading a black box that is suspiciously GUI-shaped. I've tried a few different compatibility settings and none have really worked. Last night I thought I had solved the problem, but it crashed when I opened up the project again today. The exe version of v3.0.5 had a weird bug where the GUI wouldn't update on its own and I had to drag it off screen and back on to force an update; the exe of v3.0.1 doesn't have that problem and appears to work just fine, but still fails when used as a vst.

[fundamental]

Unfortunately on windows the debugging options are fairly limited. When loading the standalone there should be a command prompt window open which can display errors which can occur. When using the plugin version though the only noteable feedback is when the UI knows that it is going to crash and just prior to crashing it should display a secondary window which shows a backtrace in the UI along with an error description.

If neither place shows the error, then unfortunately there's not much information to go off of.

As per the v3.0.5 UI having redraw issues in the standalone. I've heard of that once or twice before and know the general part of code that would be causing the issue, though I don't think it has been modified since that release to resolve the issue.

[rexendevar]

Is there another way to trace back the errors? I've heard there's a tool of some sort that helps with that but I don't remember any information about it.

[rexendevar]

Ok, I've made some observations about the behavior of 3.0.5. zynaddsubfx.exe uses a little over 50MB of memory, but is pretty light on the CPU (uses about 1-3%). zyn-fusion.exe uses a whole lot more memory, about 150MB when I initially opened the task manager, and also increases the memory use slowly over time, on the order of 10-20KB per second or so. It also goes hard cpu-wise and uses about 30-40%, except for after I created a memory dump and before I pressed a key again. It also uses about 15% of my dedicated GPU. Its window stays on top at all times, or tries to at least since I have task manager set to stay on top. the task manager window stacks on top of the zyn-fusion window. The zyn-fusion window updates unpredictably and as far as I can tell it usually has to be manually reloaded.

Here's the zynaddsubfx.exe output log I get when I run it.

Sound Buffer Size =     256 samples
Internal latency =      5.8 ms
ADsynth Oscil.Size =    1024 samples
lo server running on 11939
[INFO] Nio::start()
Starting Audio: PA
Audio Started
Starting MIDI: NULL
MIDI Started
[INFO] exec-after-init
[INFO] No Windows MIDI Device At id 0
[INFO] No Windows MIDI Device At id 1
[INFO] No Windows MIDI Device At id 2
[INFO] No Windows MIDI Device At id 3
[INFO] No Windows MIDI Device At id 4
[INFO] No Windows MIDI Device At id 5
[INFO] No Windows MIDI Device At id 6
[INFO] No Windows MIDI Device At id 7
[INFO] No Windows MIDI Device At id 8
[INFO] No Windows MIDI Device At id 9
[INFO] startup OSC
[INFO] UI calbacks
[INFO] OSC replay
[INFO] auto_save setup
[INFO] NSM Stuff
[INFO] LASH Stuff
[INFO] Launching Zyn-Fusion...
[INFO] starting subprocess via <zyn-fusion.exe osc.udp://127.0.0.1:11939/>
[INFO] Main Loop...
[INFO:Zyn] setup_pugl()
[INFO:Zyn] zest_tick()
    at this point it would simply stop until i dragged part of the main window off the edge of the screen. I tested this three times after discovering it and it was consistent.
[INFO:Zyn] zest_open()
[INFO:Zyn] Found Assets at C:\Users\me\Downloads\zyn-fusion-windows-64bit-3.0.5-release\zyn-fusion-windows-64bit-3.0.5-release\
[INFO:Zyn] Starting Zyn-Fusion
[INFO:Zyn] Thanks for supporting the developement of this project
[INFO:Zyn] Creating MRuby Interpreter...
[debug] parsing json file
[debug] json parsed succesfully
[INFO:Zyn] zest_setup()
[DEBUG:Zyn] setting up animation fps

If you think the memory dump files are also necessary to find the culprit of the issues, I can send both of the ones I made, one for each exe file.