View Issue Details

IDProjectCategoryView StatusLast Update
0001120ardourbugspublic2008-11-20 23:57
ReporterMark Knecht Assigned Totaybin  
PrioritynormalSeveritycrashReproducibilityalways
Status closedResolutionfixed 
Summary0001120: Crash using loop play
DescriptionThis happens on only one of my sessions so it may be data dependent, or possibly some session file specific issue. Hit loop play twice causes Ardour to segfault.

Back trace info below. Machine is AMD64. Kernel is 2.6.14-rc4-rt1.
Additional Informationmark@lightning ~ $ gdb ardour
GNU gdb 6.3
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "x86_64-pc-linux-gnu"...Using host libthread_db libra ry "/lib/libthread_db.so.1".

(gdb) run
Starting program: /usr/bin/ardour
[Thread debugging using libthread_db enabled]
[New Thread 46912529263712 (LWP 9592)]
[New Thread 1082132832 (LWP 9595)]
Ardour/GTK 0.9beta30
   (built using 0.603.2 with libardour 0.900.3 and GCC version 3.4.4 (Gentoo 3.4 .4-r1, ssp-3.4.4-1.0, pie-8.7.8))
Copyright (C) 1999-2005 Paul Davis
Some portions Copyright (C) Steve Harris, Ari Johnson, Brett Viren, Joel Baker

Ardour comes with ABSOLUTELY NO WARRANTY
not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
This is free software, and you are welcome to redistribute it
under certain conditions; see the source for copying conditions.
Loading UI configuration file /etc/ardour/ardour_ui.rc
Loading system configuration file /etc/ardour/ardour_system.rc
Loading user configuration file /home/mark/.ardour/ardour.rc
ardour: [INFO]: No H/W specific optimizations in use
ardour: [WARNING]: Your system generates "Mod2" when the NumLock key is pressed. This can cause problems when editing so Ardour will use Mod3 to mean Meta rathe r than Mod2

Gdk-WARNING **: Missing charsets in FontSet creation


Gdk-WARNING **: ISO8859-1

[New Thread 1090525536 (LWP 9596)]

Gdk-WARNING **: Missing charsets in FontSet creation


Gdk-WARNING **: ISO8859-1

[New Thread 1098918240 (LWP 9597)]
Loading session /home/mark/Audio/audio2/Ardour/Red-Sun using snapshot Red-Sun
[New Thread 1107310944 (LWP 9598)]
[New Thread 1115703648 (LWP 9599)]
[New Thread 1124096352 (LWP 9600)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1098918240 (LWP 9597)]
0x00000000007ad1c4 in ARDOUR::Route::process_output_buffers (this=0x193ba60,
    bufs=@0x177dee0, nbufs=1, start_frame=0, end_frame=0, nframes=0,
    offset=64, with_redirects=true, declick=0, meter=false) at route.cc:432
432 _effective_gain = gab[nframes-1];
(gdb) bt
#0 0x00000000007ad1c4 in ARDOUR::Route::process_output_buffers (
    this=0x193ba60, bufs=@0x177dee0, nbufs=1, start_frame=0, end_frame=0,
    nframes=0, offset=64, with_redirects=true, declick=0, meter=false)
    at route.cc:432
0000001 0x0000000000703f79 in ARDOUR::AudioTrack::passthru_silence (
    this=0x193ba60, start_frame=0, end_frame=0, nframes=0, offset=64,
    declick=0, meter=false) at audio_track.cc:477
#2 0x0000000000704026 in ARDOUR::AudioTrack::no_roll (this=0x193ba60,
    nframes=0, start_frame=0, end_frame=0, offset=64,
    session_state_changing=true, can_record=false, rec_monitors_input=false)
    at audio_track.cc:497
#3 0x00000000007ef067 in ARDOUR::Session::no_roll (this=0x177dc00, nframes=0,
    offset=64) at session_process.cc:103
0000004 0x00000000007efc3c in ARDOUR::Session::process_with_events (
    this=0x177dc00, nframes=0) at session_process.cc:387
0000005 0x00000000007eee30 in ARDOUR::Session::process (this=0x177dc00, nframes=64)
    at session_process.cc:62
#6 0x0000000000709c39 in ARDOUR::AudioEngine::process_callback (
    this=0xddfc80, nframes=64) at audioengine.cc:315
#7 0x000000000070974d in ARDOUR::AudioEngine::_process_callback (nframes=64,
    arg=0xddfc80) at audioengine.cc:210
0000008 0x00002aaaac30e905 in jack_client_thread (arg=0x41800d08) at client.c:1426
0000009 0x00002aaaabd110fa in start_thread () from /lib/libpthread.so.0
---Type <return> to continue, or q <return> to quit---
TagsNo tags attached.

Relationships

related to 0001196 closedtaybin crash while looping at the end of loop 
related to 0001098 closedtaybin looping with gain automation enabled crashes ardour 

Activities

StevenChamberlain

2005-11-19 01:57

reporter   ~0002382

I too experience a lot of crashes with loop play. But it only seems to happen when the click is enabled. Note that I now use version 0.99 and this bug is still present.

I can reproduce this bug every time; I create a new session and (without creating any tracks), create a loop range, enable the click track, then click on the "Play loop range" button twice. As soon as the playhead reaches the end of the loop range, Ardour crashes (for me, the Ardour window disappears without outputting anything in its terminal window).

My system is also amd64, but with kernel 2.6.12-RT-V0.7.51-29.

I was about to report the following as a seperate bug, but it sounds as though it could be the same problem:

Ardour crashes if I adjust the loop range while it is playing that loop range. Again, it will only crash when I enable the click. The Ardour window completely disappears, and on one occaision I received the following output in the terminal window:
  *** glibc detected *** malloc(): memory corruption: 0x00000000012bebb0 ***
and after loading Ardour back up and trying the same thing again:
  *** glibc detected *** double free or corruption (!prev): 0x00000000012e2260 ***
although most of the time when I do this, Ardour crashes without outputting anything to the terminal window.

taybin

2007-02-23 18:08

administrator   ~0003386

Is this still an issue?

paul

2007-03-01 19:05

administrator   ~0003454

if we get no feedback on this issue within a few days, we will close it since it is believed fixed.

Mark Knecht

2007-03-01 22:44

reporter   ~0003455

The bug report is a year and a half old. I wouldn't have a clue how to reproduce it at this point. I think it should be allowed to die from neglect if there are no similar reports elsewhere.

Close it.

taybin

2007-03-01 22:45

administrator   ~0003456

done and done.

Issue History

Date Modified Username Field Change
2005-10-12 16:27 Mark Knecht New Issue
2005-10-12 16:27 Mark Knecht E-mail => markknecht@gmail.com
2005-10-12 16:27 Mark Knecht Name => Mark Knecht
2005-11-19 01:57 StevenChamberlain Note Added: 0002382
2007-02-23 18:07 taybin Relationship added related to 0001196
2007-02-23 18:07 taybin Relationship added related to 0001098
2007-02-23 18:08 taybin Note Added: 0003386
2007-03-01 19:05 paul Note Added: 0003454
2007-03-01 22:44 Mark Knecht Note Added: 0003455
2007-03-01 22:45 taybin Status new => resolved
2007-03-01 22:45 taybin Resolution open => fixed
2007-03-01 22:45 taybin Assigned To => taybin
2007-03-01 22:45 taybin Note Added: 0003456
2008-11-20 23:57 seablade Status resolved => closed