View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0008953 | ardour | bugs | public | 2022-08-12 14:24 | 2022-08-15 21:50 |
| Reporter | FabienB | Assigned To | |||
| Priority | normal | Severity | major | Reproducibility | random |
| Status | new | Resolution | open | ||
| Platform | Ubuntu | OS | Linux | OS Version | (any) |
| Product Version | 6.9 | ||||
| Summary | 0008953: Ardour is randomly crashing with Jack server (segmentation fault) | ||||
| Description | When used with Jack server, Ardour is randomly crashing whatever the complexity of the current session (can happen with a simple audio track). It can happen a few seconds after the opening of a session or half an hour later during playback without a particular interaction. Run in a terminal, I have a "Segmentation fault" output for each crash. Here is a gdb backtrace (a part of, I can add the full BT if needed): --Type <RET> for more, q to quit, c to continue without paging-- Thread 26 "audioengine" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fffcc19f700 (LWP 3050)] 0x00007ffff7454e1b in ARDOUR::PortManager::run_input_meters(unsigned int, long) () from /opt/Ardour-6.9.0/lib/libardour.so.3 (gdb) thread apply all bt […] Thread 26 (Thread 0x7fffcc19f700 (LWP 3050)): #0 0x00007ffff7454e1b in ARDOUR::PortManager::run_input_meters(unsigned int, long) () from /opt/Ardour-6.9.0/lib/libardour.so.3 0000001 0x00007ffff745762b in ARDOUR::PortManager::cycle_start(unsigned int, ARDOUR::Session*) () from /opt/Ardour-6.9.0/lib/libardour.so.3 #2 0x00007ffff7057722 in ARDOUR::AudioEngine::process_callback(unsigned int) () from /opt/Ardour-6.9.0/lib/libardour.so.3 #3 0x00007fffcf4592fb in ARDOUR::JACKAudioBackend::process_thread() () from /opt/Ardour-6.9.0/lib/backends/libjack_audiobackend.so 0000004 0x00007fffd80491f2 in ?? () from /lib/x86_64-linux-gnu/libjack.so.0 0000005 0x00007fffd8062280 in ?? () from /lib/x86_64-linux-gnu/libjack.so.0 #6 0x00007ffff0892609 in start_thread (arg=<optimized out>) at pthread_create.c:477 #7 0x00007fffee48b133 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 […] Tested on Ubuntu 20.04.4 LTS and Ardour 6.9.0 (Official build), Jack is provided by KXStudio repository (jackd version 1.9.12). | ||||
| Tags | No tags attached. | ||||
|
|
This could have a number of causes. The backtrace is from an optimized version of Ardour (without line-numbers) so we cannot tell. A few that come to mind: * If you have any MIDI devices and hotplug them after starting Ardour, this is a known issue and fixed for upcoming Ardour 7.0. Meanwhile connect them before starting Ardour * you have manually disabled `work-around-jack-no-copy-optimization` in the config * an issue with jack 1.9.12 which is from 2017 is rather old at this point and has some known bugs that can also cause this PS. Unless you have a specific need for JACK, prefer Ardour's ALSA backend |
|
|
Thank you for your answers. I have checked the two first points and still have the problem. I do use ALSA backend for "in-the-box" projects but need sometimes Jack for bridging VCV Rack for example (VCV VST plugin does not work yet in Ardour). I will try with Ardour 7 and an updated Jack server. |
