View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0010033 | ardour | bugs | public | 2025-11-10 03:26 | 2025-11-10 03:55 |
| Reporter | delt | Assigned To | |||
| Priority | high | Severity | crash | Reproducibility | sometimes |
| Status | new | Resolution | open | ||
| Platform | Ubuntu | OS | Linux | OS Version | (any) |
| Product Version | 8.12 | ||||
| Summary | 0010033: Random crashes / X11 errors when closing LV2 plugin windows after they've been open for a while | ||||
| Description | When attempting to close the UI of a (LV2?) plugin, Ardour throws a BadGlyph X11 error and then either segfaults or exits on trap/assert. This happens mostly with Guitarix plugins especially GxAmplifier (mono and stereo) but also with others - i've even had LSP parametric EQ crash Ardour like this a few times. Happens with Ardour 8.12 and git repo of Ardour 9 - both self compiled. All of these exact same plugins / same versions are running rock solid in Carla, where this hasn't happened once as far as i can remember. I haven't thoroughly tested with VST plugins since i don't use those much, but i don't remember a specific instance where this happened to a VST2 or VST3. | ||||
| Steps To Reproduce | - load or create a project that uses, for example, a Guitarix LV2 plugin like gxAmplifier - open the UI of such a plugin, leave it open for a few minutes - maybe less if you use/tweak the UI - attempt to close the window | ||||
| Additional Information | Linux Mint 22.1, xfce on X11, dual external screens on a Lenovo laptop. | ||||
| Tags | No tags attached. | ||||
|
|
Could this be due to you patches https://discourse.ardour.org/t/how-do-i-remove-all-plugin-cache-metadata/112519 and possible memory corruption? Unlike many other LV2 hosts, Ardour does not sandbox isolate plugins, and loads the all in the same shared memory space and also runs the plugins with in-place processing. Since you compile Ardour yourself please add ASAN (adress sanitizer), which could indicate issues like that, and do a debug build (no --optimize) to get a prpoer crash report. ./waf configure --strict --ptformat --cxx17 --use-lld --backtrace --libjack=weak --address-sanitizer Please also run Ardour from the source tree debugger which may shed some light: ./gtk2_ardour/ardbg and get a backtrace of the crash if possible.. see https://ardour.org/debugging_ardour |
|
|
> i've even had LSP parametric EQ crash Ardour like this a few times. They recently also changed port-layout adding ports, which caused issues. An other possibility would be mesa 25.2.2 that can cause openGL based Plugin UIs in Ardour to crash: https://discourse.ardour.org/t/lsp-plugins-1-2-23-released/112143/79 https://tracker.ardour.org/view.php?id=10003 |
