View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000179 | ardour | bugs | public | 2003-12-09 00:35 | 2008-11-20 23:35 |
| Reporter | ndv | Assigned To | paul | ||
| Priority | normal | Severity | crash | Reproducibility | sometimes |
| Status | closed | Resolution | fixed | ||
| Summary | 0000179: Segfault when removing regions | ||||
| Description | I am very often getting a segmentation fault when I remove or cut a region. I haven't been able to work out exactly when it's happenning, as I do seem to be able to remove some regions, but I can reproduce it by starting a new session, recording one or more regions, and then trying to remove one of them. Ardour doesn't print anything out apart from "Segmentation fault". I am trying to remove them using the context menu. Is there another way I can try? This is 1.0beta8 with a relatively recent cvs JACK. | ||||
| Tags | No tags attached. | ||||
|
|
Could you post a gdb dump of this? There are instructions on how to do this in the FAQ. |
|
|
Okay, this is about all I could get out of gdb: (gdb) run Starting program: /src/ardour-0.9beta8/gtk_ardour/ardour [New Thread 16384 (LWP 1007)] [New Thread 32769 (LWP 1008)] [New Thread 16386 (LWP 1009)] Ardour/GTK 0.409.2 running with libardour 0.697.0 Loading UI configuration file /usr/local/etc/ardour/ardour_ui.rc Loading system configuration file /usr/local/etc/ardour/ardour_system.rc Loading user configuration file /root/.ardour/ardour.rc MIDI: MTC on port hw:0 MMC on port hw:0 Shift = Shift_L Shift = Shift_R Control = Control_L Control = Control_R Mod1 = Alt_L Mod2 = Num_Lock Mod3 = Mode_switch Mod4 = Meta_L Mod5 = Scroll_Lock 0 2 0 0 0 0 0 2 0 0 0 0 [New Thread 32771 (LWP 1010)] 0 736 0 367 735 0 0 736 0 367 735 0 [New Thread 49156 (LWP 1011)] Loading session /home/music/ardour/gdb_test2 using snapshot gdb_test2 [New Thread 65541 (LWP 1014)] poll interrupted ************ XRUN CALLBACK ************* ************ XRUN CALLBACK ************* [New Thread 81926 (LWP 1015)] poll interrupted ************ XRUN CALLBACK ************* ************ XRUN CALLBACK ************* adding 1 new routes Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 16384 (LWP 1007)] 0x0836f3ed in RegionSelection::add () Current language: auto; currently c++ (gdb) thread apply all bt Cannot find new threads: generic error (gdb) bt #0 0x0836f3ed in RegionSelection::add () Error accessing memory address 0x836f120: No such process. (gdb) quit A debugging session is active. Do you still want to close the debugger?(y or n) y Cannot find thread 16384: generic error (gdb) Interestingly, before the crash the output of `ps aux | grep jackd` before the crash looks like root 986 0.0 4.0 10240 10232 ? SL 14:35 0:00 jackd --realtime -d alsa -d soundblaster -r 44100 -p 1024 -n 2 root 987 0.0 4.0 10240 10232 ? SL 14:35 0:00 jackd --realtime -d alsa -d soundblaster -r 44100 -p 1024 -n 2 root 988 0.0 4.0 10240 10232 ? SL 14:35 0:00 jackd --realtime -d alsa -d soundblaster -r 44100 -p 1024 -n 2 root 989 0.0 4.0 10240 10232 ? SL 14:35 0:00 jackd --realtime -d alsa -d soundblaster -r 44100 -p 1024 -n 2 root 990 0.2 4.0 10240 10232 ? SL 14:35 0:00 jackd --realtime -d alsa -d soundblaster -r 44100 -p 1024 -n 2 root 1017 0.0 0.1 1288 416 pts/3 S 14:39 0:00 grep jackd but afterwards it's root 986 0.0 3.2 8192 8188 ? SL 14:35 0:00 jackd --realtime -d alsa -d soundblaster -r 44100 -p 1024 -n 2 root 987 0.0 0.0 0 0 ? Z 14:35 0:00 [jackd <defunct>] root 1019 0.0 0.1 1288 416 pts/3 S 14:39 0:00 grep jackd |
|
|
I get this same error, but I haven't done any gdb backtraces. I start a new session, add a single track, record 1 measure, then click the region and hit DELETE on the keyboard. Segfault. |
|
|
Is this still a problem? |
|
|
Reminder sent to ndv Does bug:179 still exist with the latest ardour tarball? |
|
|
Hi, sorry I didn't reply before, I was out of the country for a while with no linux box... I just tried the latest Ardour a few days ago and it didn't seem to have this problem any more. I'll probably be using it some more over the next couple of weeks so if it does turn up again I'll let you know. |
|
|
appears resolved according to reporter. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2003-12-09 00:35 | ndv | New Issue | |
| 2003-12-11 15:21 | taybin | Note Added: 0000258 | |
| 2003-12-11 15:21 | taybin | Status | new => acknowledged |
| 2003-12-14 14:46 | ndv | Note Added: 0000296 | |
| 2003-12-17 06:08 | Jaymz031602 | Note Added: 0000315 | |
| 2004-02-10 15:58 | taybin | Note Added: 0000402 | |
| 2004-04-20 16:37 | taybin | Note Added: 0000642 | |
| 2004-04-21 10:30 | ndv | Note Added: 0000653 | |
| 2004-04-21 11:26 | paul | Status | acknowledged => resolved |
| 2004-04-21 11:26 | paul | Resolution | open => fixed |
| 2004-04-21 11:26 | paul | Assigned To | => paul |
| 2004-04-21 11:26 | paul | Note Added: 0000654 | |
| 2008-11-20 23:35 | seablade | Status | resolved => closed |
