Add new comment

try running under gdb (you have gdb installed, correct?):

when the crash happens, probably due a SIGSEGV interrupt, gdb prompt gets back to you, then:

do capture the stack-trace output and paste it somewhere for further analisys...

it sure helps (a lot) if you have debug symbols available (usually provided by respective "qtractor-debug*" package, or you have built it from source from ./configure --enable-debug).

at this time, and with the (no) information given, it is useless to speculate what the problem is, but sure it's a component on the offending session file (*.qt?), most probably an ill-behaved or faulty plugin, someway or another.

hth
cheers