View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0008904 | ardour | bugs | public | 2022-04-22 16:23 | 2022-04-23 10:54 |
| Reporter | robertaramar | Assigned To | |||
| Priority | normal | Severity | crash | Reproducibility | always |
| Status | new | Resolution | open | ||
| Platform | Redhat | OS | Linux | OS Version | (any) |
| Product Version | 6.9 | ||||
| Summary | 0008904: Ardour crashes after some time | ||||
| Description | Running Ardour on JACK. No matter whether buffers are big 512 or small 64. After some time, I get an exception and Ardour crashes. I do not get this when running Ardour on ALSA. As I ususally use ALSA, but did have to use JACK in this particular case, this bug is not really important to me. I just thought, Ardour shouldn't crash for anything like that. | ||||
| Steps To Reproduce | No particular steps to be taken. I don't even have to play anything, just launching Ardour with a project and leave it, will crash shortly after one minute (01:09, 01:15). You have to open a project, having the project selection box open, does not count into that minute. | ||||
| Additional Information | [Thread 0x7fffaffff640 (LWP 104142) exited] Thread 25 "audioengine" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fffc4367640 (LWP 104179)] 0x00007ffff744ce1b in ARDOUR::PortManager::run_input_meters(unsigned int, long) () from /opt/Ardour-6.9.0/lib/libardour.so.3 (gdb) bt #0 0x00007ffff744ce1b in ARDOUR::PortManager::run_input_meters(unsigned int, long) () from /opt/Ardour-6.9.0/lib/libardour.so.3 0000001 0x00007ffff744f62b in ARDOUR::PortManager::cycle_start(unsigned int, ARDOUR::Session*) () from /opt/Ardour-6.9.0/lib/libardour.so.3 #2 0x00007ffff704f722 in ARDOUR::AudioEngine::process_callback(unsigned int) () from /opt/Ardour-6.9.0/lib/libardour.so.3 #3 0x00007fffc71c12fb in ARDOUR::JACKAudioBackend::process_thread() () from /opt/Ardour-6.9.0/lib/backends/libjack_audiobackend.so 0000004 0x00007fffdc015414 in non-virtual thunk to Jack::JackClient::Execute() () at ../common/JackClient.cpp:583 0000005 0x00007fffdc0330b0 in Jack::JackPosixThread::ThreadHandler (arg=0x555556a99f98) at ../posix/JackPosixThread.cpp:63 #6 0x00007fffee422b1a in start_thread (arg=<optimized out>) at pthread_create.c:443 #7 0x00007fffee4a7660 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 | ||||
| Tags | No tags attached. | ||||
|
|
Almost certainly caused by JACK "zombifying" Ardour for taking too long when processing audio OR by JACK itself going away. Will hopefully be fixed in 7.0, but it is actually remarkably difficult for JACK clients as complex as Ardour to respond safely to either of those two conditions. |
|
|
Would you think that is something introduced by JACK lately. Because I'm using Ardour 6.9.0 since it came out, I was using it solely on JACK until I switch to using ALSA - roughly - six months ago. And I never had issues with JACK before. If I can be of help further analyzing that, please let me know. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2022-04-22 16:23 | robertaramar | New Issue | |
| 2022-04-22 18:11 | paul | Note Added: 0026413 | |
| 2022-04-23 10:54 | robertaramar | Note Added: 0026417 |
