View Issue Details

IDProjectCategoryView StatusLast Update
0003525ardourbugspublic2010-11-11 16:06
Reporter2handband Assigned To 
PrioritynormalSeveritycrashReproducibilitysometimes
Status confirmedResolutionopen 
Product Version2.8.11 
Summary0003525: Ardour crashes with segmentation fault when I attempt to load an existing session
DescriptionI'm using Ardour 2.8.11, which I built from source on my Slackware 13.1 system. When I try to open an existing session Ardour is crashing more often than not with a segmentation fault. I usually have to make three or four tires to get something to load up. Here's the output:

loading default ui configuration file /usr/local/etc/ardour2/ardour2_ui_default.conf
loading user ui configuration file /home/gene/.ardour2/ardour2_ui.conf
Loading ui configuration file /usr/local/etc/ardour2/ardour2_ui_dark.rc
theme_init() called from internal clearlooks engine
ardour: [INFO]: Ardour will be limited to 1024 open files
loading system configuration file /usr/local/etc/ardour2/ardour_system.rc
loading user configuration file /home/gene/.ardour2/ardour.rc
ardour: [INFO]: Using SSE optimized routines
ardour: [INFO]: looking for control protocols in /home/gene/.ardour2/surfaces/:/usr/local/lib64/ardour2/surfaces/
ardour: [INFO]: Control protocol Tranzport not usable
ardour: [INFO]: Control surface protocol discovered: "Mackie"
powermate: Opening of powermate failed - No such file or directory
ardour: [INFO]: Control protocol powermate not usable
ardour: [INFO]: Control surface protocol discovered: "Generic MIDI"
Segmentation fault
TagsNo tags attached.

Activities

cth103

2010-11-07 02:32

administrator   ~0009371

There is a known bug with zoom that can cause this problem. Try editing the "instant.xml" file inside your session directory with a text editor and changing the number after "zoom=" to something like 256.

If this doesn't help, please either

a) attach the session to this bug (you don't need to include sound files)
or b) rebuild Ardour with debugging enabled (see http://ardour.org/debugging_ardour) and get a backtrace.

2handband

2010-11-07 15:33

reporter   ~0009374

Changing the zoom fixed it, but also put the zoom in a place I don't really want it (I like my playhead to move slowly). I'm gonna rebuild Ardour with debug as soon as I figure out a scons uninstall.

paul

2010-11-08 21:44

administrator   ~0009381

there's not much point in a debug build. this is a long-standing bug (years and years) and it won't be illuminated by anything you can find with a debug build. its not likely to ever be fixed in ardour2, and likely will not be fixed until we switch to a new canvas in ardour4.

2handband

2010-11-08 22:27

reporter   ~0009382

workarounds?

paul

2010-11-08 23:13

administrator   ~0009383

there are no workarounds. nothing stops you from using more zoomed-in levels or more zoomed-out levels, but saving the session when fully zoomed-in (or close to it) has this issue. its not deterministic, but it is frequent.

Issue History

Date Modified Username Field Change
2010-11-07 01:48 2handband New Issue
2010-11-07 02:32 cth103 Note Added: 0009371
2010-11-07 02:32 cth103 Status new => feedback
2010-11-07 15:33 2handband Note Added: 0009374
2010-11-08 21:44 paul Note Added: 0009381
2010-11-08 22:27 2handband Note Added: 0009382
2010-11-08 23:13 paul Note Added: 0009383
2010-11-11 16:06 paul Status feedback => confirmed