View Issue Details
|ID||Category||Date Submitted||Last Update|
|0008415||bugs||2020-09-18 20:27||2020-10-19 00:55|
|Reporter||Fruit tree||Assigned To|
|Fixed in Version|
|Summary||0008415: Ardour crashes sometimes when I stop playback|
|Description||$ Ardour6 --version|
bind txt domain [gtk2_ardour6] to /opt/Ardour-6.3.8-dbg/share/locale
Ardour6.3.8 (built using 6.3-8-gf61ecae4b2 and GCC version 6.3.0 20170516)
It's from the nightly builds page, with debug symbols allegedly.
I think this is an instance of a bug that crashes ardour within minutes every time I use it.
It always happens when I stop playback (pressing space). (But not every time I do this)
This time I was finally prepared with a debug build and coredumpctl. I thought. So I ran `coredumpctl debug` after the crash, and in gdb I wrote `thread apply all bt` and just `bt`; both just say a lot of:
Thread 41 (LWP 176868):
#0 0x00007f07a64696a2 in ?? ()
Backtrace stopped: Cannot access memory at address 0x7f0782c0db80
.. So it doesn't have debug symbols?
I'm saving the coredump and I would be very happy if someone could help me extract some useful information out of it, or set up my system to get more useful information next time this bug happens!
|Tags||No tags attached.|
Update: Opened the same project, pressed space to play then space to stop, and it happened again.
So, as I suspected before, I think the reproducibility is 100% reproducible on my machine for a certain project, from some point in time and forth.
A bit more detail: when it happens, there's a buzzing sound for about 10 seconds and this time my system froze completely until Ardour finally exited.
||Update: This happens only with JACK backend, not ALSA. (but I won't use ALSA)|
I have been having the same bug, only for me it happens fairly often. Often enough to make using ardour extremely frustrating.
I am running version 6.3.0 built using 6.3 and GCC Version 10.2.0, straight from the Arch Linux repositories. (Package version 6.3.0-2). It's been happening since I upgraded from 5.x to 6.x.
I use JACK exclusively.
If a recently nightly still produces this issue, please try if you can get it to crash while running in gdb, start it: Ardour6 --gdb
in gdb: run
see also https://ardour.org/debugging_ardour "Option 1: Running Ardour inside GDB"