View Issue Details

IDCategoryLast Update
0006878bugs2016-05-19 18:39
ReportermagnetophonAssigned To 
Reproducibilityalways 
Status newResolutionopen 
PlatformlinuxOSNixOSOS Version16.03
Product Version4.7 
Fixed in Version 
Summary0006878: session that always crashes
DescriptionThe attached session crashes with the message:

spectr.lv2: shifted to f:19937.36Hz (17824.72Hz -> 22050.00Hz)
Set buffering params to 262144|131072|10|10
Skip explicit buffer seconds, preset in use
Skip explicit buffer seconds, preset in use
ardour-4.7.d84a8222: malloc.c:2395: sysmalloc: Assertion `(old_top == initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)' failed.
[1] 16167 abort ardour4 /media/sdc6/Karikatura/BlackSheep/BlackSheep.ardour

The last thing I did afaik, is add insert1.
Steps To ReproduceJust load the session.
TagsNo tags attached.

Activities

magnetophon

2016-05-17 11:28

reporter  

BlackSheep.ardour (501,372 bytes)

x42

2016-05-17 11:59

administrator   ~0018204

I do miss nearly all of the plugins in that session and it loads just fine here.
Can you produce a backtrace that leads to the crash?

Does it load with `ardour4 --disable-plugins` ?

If not, try to move instant.xml and *.history files out of the way.
A crash in malloc could be an out-of-[lockable]-memory, but this assert smells more like memory corruption.

magnetophon

2016-05-19 18:11

reporter   ~0018207

I forgot why, but I've been unable to produce an Ardour backtrace on NixOS in the past.

The session loads fine without plugins.

Oddly, the session also loads if I remove "insert 1" in a text editor.

x42

2016-05-19 18:39

administrator   ~0018208

Is there maybe a 2nd "insert 1" already present? or an "insert 0"?

There was a bug with numbering sends (fixed in 4.7-825-gf719dcb).

Duplicate send ID -> duplicate port-name "[jack] port cannot be created" -> undefined behavior. In that case there should be a message in the terminal "Port creation failed.."

If not, possibly some plugin-related concurrency issue when loading the session and send indirectly triggers it and it'll be hard to track that down w/o a backtrace.

Issue History

Date Modified Username Field Change
2016-05-17 11:28 magnetophon New Issue
2016-05-17 11:28 magnetophon File Added: BlackSheep.ardour
2016-05-17 11:59 x42 Note Added: 0018204
2016-05-19 18:11 magnetophon Note Added: 0018207
2016-05-19 18:39 x42 Note Added: 0018208