Bug 176

Summary: LS segfaults Ardour3 on session load, backtrace attatched
Product: LinuxSampler Reporter: gabbe.nord
Component: otherAssignee: Andreas Persson <andreas56>
Status: CLOSED DUPLICATE    
Severity: critical CC: andreas56, cuse
Priority: P5    
Version: SVN Trunk   
Hardware: PC   
OS: Linux   

Description gabbe.nord 2012-02-06 18:34:57 CET
LinuxSampler crashes Ardour3 at session load. I've confirmed with the Ardour-devs that this is indeed a LinuxSampler-issue. I have also confirmed that some others have the same issue. Eventually it works, after trying to load the session ~5 times. 

I'm using latest svn of LinuxSampler and Ardour3.

It's a session with several (~5) LinuxSampler lv2-plugins loaded. 

Here's a backtrace from Ardour3-dbg:

[New Thread 0x7fffc0367700 (LWP 6427)]
[Thread 0x7fffc3066700 (LWP 6426) exited]
Loading LV2 state from /home/zth/PARTYLIMER/plugins/159133/state1/state.ttl
[Thread 0x7fffc0367700 (LWP 6427) exited]
[New Thread 0x7fffc3066700 (LWP 6428)]
Stopping disk thread...OK
[Thread 0x7fffc3066700 (LWP 6428) exited]
Starting disk thread...[New Thread 0x7fffc3066700 (LWP 6429)]
OK
EQ support: no
[Thread 0x7fffc3066700 (LWP 6429) exited]
[New Thread 0x7fffc0367700 (LWP 6430)]
Scheduling '/home/zth/SAMPLES/Instruments/SalamanderGrandPianoV2_48khz24bit/SalamanderGrandPianoV2.sfz' (Index=0) to be loaded in background (if not loaded yet).
Loading sfz file '/home/zth/SAMPLES/Instruments/SalamanderGrandPianoV2_48khz24bit/SalamanderGrandPianoV2.sfz'...Loading LV2 state from /home/zth/PARTYLIMER/plugins/159133/state1/state.ttl
[Thread 0x7fffc0367700 (LWP 6430) exited]
[New Thread 0x7fffc3066700 (LWP 6431)]
Stopping disk thread...OK
[Thread 0x7fffc3066700 (LWP 6431) exited]
OK
Loading sfz instrument ('/home/zth/SAMPLES/Instruments/SalamanderGrandPianoV2_48khz24bit/SalamanderGrandPianoV2.sfz',0)...OK
Caching initial samples...Starting disk thread...[New Thread 0x7fffc3066700 (LWP 6432)]
OK
EQ support: no
[New Thread 0x7fffc0367700 (LWP 6433)]
[Thread 0x7fffc3066700 (LWP 6432) exited]
Scheduling '/home/zth/SAMPLES/Instruments/SalamanderGrandPianoV2_48khz24bit/SalamanderGrandPianoV2.sfz' (Index=0) to be loaded in background (if not loaded yet).
[New Thread 0x7fffabf7e700 (LWP 6434)]
[New Thread 0x7fffaae33700 (LWP 6435)]
Multi-core: got real-time scheduling with priority 65
[New Thread 0x7fffaa632700 (LWP 6436)]
[Thread 0x7fffaa632700 (LWP 6436) exited]
[New Thread 0x7fffaa632700 (LWP 6437)]
[New Thread 0x7fffc3066700 (LWP 6438)]
SHOW UI 1852011892 editor: 1
[New Thread 0x7fffa90fd700 (LWP 6439)]
[New Thread 0x7fffa88fc700 (LWP 6440)]
OK

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffc3168700 (LWP 6384)]
0x00007fffc38c5c32 in LinuxSampler::sfz::InstrumentResourceManager::Create (
    this=0x7fffc3bd2cc0, Key=DWARF-2 expression error: DW_OP_reg operations must be used either alone or in conjuction with DW_OP_piece or DW_OP_bit_piece.
) at InstrumentResourceManager.cpp:150
150	InstrumentResourceManager.cpp: No such file or directory.
	in InstrumentResourceManager.cpp
(gdb) bt
#0  0x00007fffc38c5c32 in LinuxSampler::sfz::InstrumentResourceManager::Create
    (this=0x7fffc3bd2cc0, Key=DWARF-2 expression error: DW_OP_reg operations must be used either alone or in conjuction with DW_OP_piece or DW_OP_bit_piece.
) at InstrumentResourceManager.cpp:150
#1  0x00007fffc38cd752 in Borrow (this=0x7fff9abd4c60)
    at ../../common/ResourceManager.h:216
#2  LinuxSampler::sfz::EngineChannel::LoadInstrument (this=0x7fff9abd4c60)
    at EngineChannel.cpp:108
#3  0x00007fffc3903a1a in LinuxSampler::InstrumentManagerThread::Main (
    this=0x7fffc3bd3100) at InstrumentManagerThread.cpp:119
#4  0x00007fffc395e7b4 in LinuxSampler::__pthread_launcher (
    thread=0x7fffc3bd3100) at Thread.cpp:398
#5  0x00007fffec430d8c in start_thread ()
   from /lib/x86_64-linux-gnu/libpthread.so.0
#6  0x00007fffec17c04d in clone () from /lib/x86_64-linux-gnu/libc.so.6
#7  0x0000000000000000 in ?? ()
(gdb)
Comment 1 Andreas Persson 2012-03-10 20:42:12 CET
I think this is the same as #157, and I also think I have fixed it now.

*** This bug has been marked as a duplicate of bug 157 ***