View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0002350ardourbugspublic2008-07-20 06:572010-04-25 15:20
ReporterMax Littlemore Assigned To 
PrioritynormalSeveritycrashReproducibilityalways
Status feedbackResolutionopen 
Product VersionSVN/2.0-ongoing 
Summary0002350: Ardour crashes trying to load a project - cannot recover
DescriptionI was working on a project with three buses containing different reverbs and using post fader sends to to route multiple channels to these buses.

I renamed the sends to make it easy to see where they route to, giving all of the sends to a particular bus the same name (e.g "2 q reflect").

I saved the project and the next time I tried to open it, ardour segfaulted. I cannot recover this project without hacking the project xml and removing the history and all of the snapshots are from before I recorded some important tracks.

If there is any more info needed, please let me know. I will hang onto the bad project file. Also, I'm not sure if this is logged under the right version, if not sorry.
Additional InformationFrom Help > About:
 ardour 2.3
 (built from revision 3029)

from standard repos - UbuntuStudio 8.04

The project file is attached.

output running in shell:

maxl@compoota:~/Media/Music/slap bang/ufo$ ardour2
WARNING: Your system has a limit for maximum amount of locked memory!
This might cause Ardour to run out of memory before your system runs out of memory. You can view the memory limit with 'ulimit -l', and it is normally controlled by /etc/security/limits.conf
Ardour/GTK 2.3
   (built using 3029 and GCC version 4.2.3 (Ubuntu 4.2.3-1ubuntu2))
Copyright (C) 1999-2007 Paul Davis
Some portions Copyright (C) Steve Harris, Ari Johnson, Brett Viren, Joel Baker

Ardour comes with ABSOLUTELY NO WARRANTY
not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
This is free software, and you are welcome to redistribute it
under certain conditions; see the source for copying conditions.
theme_init() called from internal clearlooks engine
/usr/share/themes/Glossy/gtk-2.0/gtkrc:62: error: unexpected identifier `colorize_scrollbar', expected character `}'
loading default ui configuration file /etc/ardour2/ardour2_ui_default.conf
loading user ui configuration file /home/maxl/.ardour2/ardour2_ui.conf
Loading ui configuration file /etc/ardour2/ardour2_ui_dark.rc
theme_init() called from internal clearlooks engine
loading system configuration file /etc/ardour2/ardour_system.rc
loading user configuration file /home/maxl/.ardour2/ardour.rc
ardour: [INFO]: No H/W specific optimizations in use
ardour: [INFO]: looking for control protocols in /home/maxl/.ardour2/surfaces/:/usr/lib/ardour2/surfaces/
ardour: [INFO]: Control surface protocol discovered: "Mackie"
ardour: [INFO]: Control surface protocol discovered: "Generic MIDI"
powermate: Opening of powermate failed - No such file or directory
ardour: [INFO]: Control protocol powermate not usable
Enhanced3DNow! detected
SSE2 detected
Enhanced3DNow! detected
SSE2 detected
loading bindings from /home/maxl/.ardour2/ardour.bindings
Loading session /home/maxl/Media/Music/slap bang/ufo using snapshot ufo (1)
Segmentation fault
TagsNo tags attached.

Activities

2008-07-20 06:57

 

ufo.ardour (210,607 bytes)

cth103

2010-04-25 15:20

administrator   ~0007536

This should be (kind of) fixed now. The problem is the multiple sends with the same name; Ardour now prevents you from creating such sends in the first place, and should give a more informative error message (rather than a segfault) with your broken session.

Can you say whether current Ardour versions are any better for you in this regard?

Issue History

Date Modified Username Field Change
2008-07-20 06:57 Max Littlemore New Issue
2008-07-20 06:57 Max Littlemore File Added: ufo.ardour
2010-04-24 10:28 cth103 Category bugs => bugs2
2010-04-24 10:32 cth103 Category bugs2 => bugs
2010-04-25 15:20 cth103 Note Added: 0007536
2010-04-25 15:20 cth103 Status new => feedback