I do undertstand that there’s probably not much bug fixing going on with V1
I just ran into this again with a particular patch. If I exit and then re-run Rack, this patch crashes every time. If I start over with a blank patch, I can load the rack patch.
Nothing in log.txt about an exception or abort. It looks like all the modules load their resources and initialize and the log just ends.
This is the patch for what it’s worth. You won’t probably have some of my plugins.
2021-10-04.vcv (958.8 KB)
It does the same thing for me but I do get some log info:
[0.632 fatal src/main.cpp:45] Fatal signal 11. Stack trace:
7: /home/alex/.local/opt/Rack/Rack() [0x56d2b1]
6: /lib/x86_64-linux-gnu/libc.so.6(+0x46210) [0x7efee5a89210]
5: /home/alex/.Rack/plugins-v1/squinkylabs-plug1/plugin.so(+0x1f4d1e) [0x7efea4c4dd1e]
4: /home/alex/.local/opt/Rack/Rack() [0x5b5da3]
3: /home/alex/.local/opt/Rack/Rack(_ZN4rack6engine12EngineWorker3runEv+0x15e) [0x5b7200]
2: /usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0xd7172) [0x7efee5e78172]
1: /lib/x86_64-linux-gnu/libpthread.so.0(+0x9609) [0x7efee6878609]
0: /lib/x86_64-linux-gnu/libc.so.6(clone+0x43) [0x7efee5b65293]
Doesn’t seem particularly helpful. I tried to narrow it down but couldn’t find what causes it (meaning that if squinkylabs is the cause then it is because of something that’s interacting with it, it’s not those modules alone).