jalv segfaults when applying preset

[rekado]

I get a segfault in jalv after applying a preset from the menu. This applies to presets saved by jalv and those bundled with the plugin.

JACK version: 1.9.8 (with dbus support)

Backtrace:

#0  0x00007ffff7162260 in jack_ringbuffer_write_space () from /usr/lib/libjack.so.0
#1  0x00007ffff716248d in jack_ringbuffer_write () from /usr/lib/libjack.so.0
#2  0x000000000040549e in jalv_ui_write ()
#3  0x0000000000406cd5 in set_port_value ()
#4  0x00007ffff7bcf337 in lilv_state_restore () from /usr/local/lib/liblilv-0.so.0
#5  0x0000000000406da7 in jalv_apply_state ()
#6  0x0000000000406e03 in jalv_apply_preset ()
#7  0x0000000000407a36 in on_preset_activate ()

I'm not sure if a segfault in jalv is ever justified if the plugin is broken. (I'm testing with ​http://elephly.net/lv2/mdaEPiano, which may or may not be broken.)

[dave]

Works fine for me with calf Monosynth...

Please use a debug build.

[rekado]

gdb backtrace when running jalv with calf monosynth

[rekado]

The same happens with calf monosynth. Full backtrace attached.
(I'm using a slightly older but working version from git, as my ISP blocks git access to repo.or.cz.)

[dave]

I'm guessing this is a Jack2 problem, or a dirty build...

[rekado]

I'm also getting this message during start-up:

warning: Old JACK, using default MIDI buffer size 4096

Does this mean that jalv erroneously assumes I use Jack1?

[rekado]

I removed jack2, installed jack1 through the distro package manager, cleaned the build, configured, made, and installed the whole lad repo, but I still get the very same segfault.

[dave]

Aahh, when running without a UI.

Fixed in r3956.

(Also, ticket 808! Boom boom boom boom)

[rekado]

Just tested with both plugins: it's fixed.

(Couldn't test further because of the segfault reported in #802, but selecting a preset doesn't crash jalv anymore.)