PlugdataFX VST3 crashes when copying the FX device in Renoise

Help, Support & Bugs
1

I got plugdata for Ubuntu from here:

https://software.opensuse.org//download.html?project=home%3Aplugdata&package=plugdata

When copying the plugdataFX plugin (select with middle mouse key and Ctrl+C) Renoise crashes with these log messages:

Vst3Plugs: Instantiating: /usr/lib/vst3/plugdata-fx.vst3...

CrashLog: Caught signal: SIGSEGV (11) ...
CrashLog: /lib/x86_64-linux-gnu/libc.so.6(+0x45320) [0x73e8cb445320]
CrashLog: /usr/lib/vst3/plugdata-fx.vst3/Contents/x86_64-linux/plugdata-fx.so(+0x7ac55b) [0x73e843dac55b]
CrashLog: /usr/lib/vst3/plugdata-fx.vst3/Contents/x86_64-linux/plugdata-fx.so(+0x6d8409) [0x73e843cd8409]
CrashLog: /usr/lib/vst3/plugdata-fx.vst3/Contents/x86_64-linux/plugdata-fx.so(+0x3f983b) [0x73e8439f983b]
CrashLog: /usr/lib/vst3/plugdata-fx.vst3/Contents/x86_64-linux/plugdata-fx.so(+0x3f34a3) [0x73e8439f34a3]
CrashLog: /usr/lib/vst3/plugdata-fx.vst3/Contents/x86_64-linux/plugdata-fx.so(+0x20d628) [0x73e84380d628]
CrashLog: /usr/lib/vst3/plugdata-fx.vst3/Contents/x86_64-linux/plugdata-fx.so(+0x42ad25) [0x73e843a2ad25]
CrashLog: /lib/x86_64-linux-gnu/libc.so.6(+0x9ca94) [0x73e8cb49ca94]
CrashLog: /lib/x86_64-linux-gnu/libc.so.6(+0x129c3c) [0x73e8cb529c3c]
CrashLog: [(nil)]
CrashLog: [0x333233326666223d]

grafik

2

It’s plugdata that crashes here after collecting its preset data, but this may be a problem with other plugins too, so we should fix this.

Currently, Renoise creates a temporary copy of the plugin in order to load and save the plugin’s preset data to the clipboard. This should generally work, but is also quite a stress test for plugins and thus makes crashes in plugins more likely. I’ll try to avoid this, also to speed up the “copy” process.

3 Likes
3

I will do some more tests tomorrow. It was also very erratic in Reaper. Will check Bitwig aswell.

4

If you want to report this, report this to the Plugdata FX crew instead.

5

I did, but no reply yet. So, either you can fix it or it can be fixed in the Plugin?

6

I think it would be better to report it on github issue or on the plugdata-issues channel on discord, but I can’t seem to find it. Where did you report it?

7

I reported it on the Dicord Channel in the Linux section of plugdata

8

If it is about the #linux-packages channel, I have a feeling that it will unfortunately get almost no attention because it is not an issue.

EDIT: Sorry, this means that it may not get attention unless it goes through some communication channel associated with the word issues.

9

That’s also my feeling. But why do they make a Linux version then?

10

Sorry, maybe it’s because I’m talking through a translation service, but there seems to be a bit of a communication discrepancy.
What I think would be best would be to report something like what you wrote in the OP of this thread to the github issues with some additional information such as the version number of the relevant software you are using.

Then the plugdata development team will take care of it in time.

1 Like
11

Will do this tomorrow :+1:

12

It is better to write a ticket with information about the OS you are using and the relevant software and kernel version, and then ask in the #plugdata-issues channel if that is the correct way to write the ticket or if you need additional information, etc.
That way, it would probably get the attention it needs without any problems.

1 Like
13
14

Already fixed! :smiley:

15

great

1 Like
16

They are verry active on discord , in fact it’s the only active place for all things plug-data

17

That honestly looks more like a plugdata issue than Renoise itself. The crash is happening inside plugdata-fx.so, and Renoise is basically just triggering it when duplicating the device state.

I’ve seen a few Linux VST3 plugins behave badly when copied or cloned, especially with JUCE-based plugins. Sometimes the plugin doesn’t properly handle state duplication and Renoise exposing that causes the segfault.

try these things:

  • test the LV2 or VST2 version instead of VST3 if available

  • try the official build from the plugdata GitHub/releases instead of the OpenSUSE package

  • disable plugin sandboxing/bridging temporarily and see if behavior changes

  • save the FX as a preset first, then load a second instance manually instead of copy/paste

But from that stack trace, I’d definitely report it to the plugdata devs too.