View Issue Details

IDProjectCategoryView StatusLast Update
0004227ardourbugspublic2020-04-19 20:15
Reporternandinga Assigned Tocth103  
PrioritynormalSeveritycrashReproducibilityrandom
Status closedResolutionunable to reproduce 
PlatformUbuntuOSLinuxOS VersionMaverick
Target Version3.0-beta1 
Summary0004227: Ardour randomly crashes on startup
DescriptionIt works sometimes, it sometimes crash. When running inside GDB (ardbg), it works more than it fails. If running ardev it crashes 2 or 3 times for each success.


(gdb) run
The program being debugged has been started already.
Start it from the beginning? (y or n) y

Starting program: /home/nando/workspace/ardour/3.0/build/default/gtk2_ardour/ardour-3.0
[Thread debugging using libthread_db enabled]
Ardour3.0alpha9 (built using ['9915'] and GCC version 4.4.5)
Copyright (C) 1999-2011 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.
Cannot xinstall SIGPIPE error handler
ardour: [INFO]: Loading default ui configuration file ./../gtk2_ardour/ardour3_ui_default.conf
Loading user ui configuration file /home/nando/.config/ardour3/ardour3_ui.conf
ardour: [INFO]: Loading ui configuration file ./../build/default/gtk2_ardour/ardour3_ui_dark.rc

Program received signal SIGSEGV, Segmentation fault.
0xb5d168b4 in ?? () from /lib/libglib-2.0.so.0
(gdb) thread apply all bt

Thread 1 (Thread 0xb40ea880 (LWP 24659)):
#0 0xb5d168b4 in ?? () from /lib/libglib-2.0.so.0
0000001 0xb5d16a94 in g_build_filename () from /lib/libglib-2.0.so.0
#2 0xb5812383 in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#3 0xb58126ed in ?? () from /usr/lib/libgtk-x11-2.0.so.0
0000004 0xb5812864 in ?? () from /usr/lib/libgtk-x11-2.0.so.0
0000005 0xb5812b58 in gtk_rc_parse () from /usr/lib/libgtk-x11-2.0.so.0
#6 0xb50bce95 in Gtk::RC::RC(Glib::ustring const&) ()
   from /usr/lib/libgtkmm-2.4.so.1
#7 0xb661ddce in Gtkmm2ext::UI::load_rcfile (this=0x995c528, path=...,
    themechange=false) at ../libs/gtkmm2ext/gtk_ui.cc:156
0000008 0x092d6421 in load_rc_file (filename=..., themechange=false)
    at ../gtk2_ardour/theme_manager.cc:205
0000009 0x092d6d71 in ThemeManager::setup_theme (this=0x9a24568)
    at ../gtk2_ardour/theme_manager.cc:287
0000010 0x092d51eb in ThemeManager::ThemeManager (this=0x9a24568,
    __in_chrg=<value optimized out>, __vtt_parm=<value optimized out>)
    at ../gtk2_ardour/theme_manager.cc:99
0000011 0x08b09b0c in ARDOUR_UI::ARDOUR_UI (this=0x995c528, argcp=0xbfffeb00,
    argvp=0xbfffeb04, __in_chrg=<value optimized out>,
    __vtt_parm=<value optimized out>) at ../gtk2_ardour/ardour_ui.cc:205
0000012 0x08f7e591 in main (argc=1, argv=0xbfffeba4)
    at ../gtk2_ardour/main.cc:551
(gdb)
TagsNo tags attached.

Activities

paul

2011-07-24 20:19

administrator   ~0011204

this looks faily unpromising as far as reproducability. what does ulimit -l say on your system?

nandinga

2011-07-24 20:39

reporter   ~0011205

$ ulimit -l
unlimited

It doesn't happen to me on alpha9 installed from the packaged version posted on the web.

paul

2011-07-24 20:43

administrator   ~0011206

i think you may need to run this under valgrind to get any useful information. there is a script in the gtk2_ardour folder (similar to ./ardbg) called "arval" that will do this if you have valgrind installed. it will run MUCH slower and you must ensure that JACK is not in RT mode and has a long client timeout (-t 50000 is good). this may show what is going on better than gdb. or it may not.

nandinga

2011-07-24 21:11

reporter   ~0011208

Hmm... I've tried it 10 times in a row with arval and haven't had any crashes. Also tested it 3 more times with high CPU load from other processes (no idea if it helps but... it was my wild guess hehe). No crashes there either.

Seems like the probability of a crash diminishes as the execution gets slower.

The crash is even before the alpha version warning dialog appears, so tried without Jack enabled (no need to look RT or -t).

nandinga

2011-07-24 21:12

reporter   ~0011209

I'm on irc now.

paul

2011-08-11 16:29

administrator   ~0011297

did we figure this one out on IRC?

nandinga

2011-08-11 22:39

reporter   ~0011303

Nop. This is the status right now.

I'll not be available for a couple of days but I'll get back to this and let you know.

nandinga

2011-09-20 20:05

reporter   ~0011545

tested alpha10 binary and it doesn't show the problem

it's probably an issue with my personal gtk installation, so when i upgrade those (when there is a new -usable- version of ubuntu :p) i'll test again, and close this if the problem disappears.

cth103

2011-10-22 23:21

administrator   ~0011740

I'll mark this as closed for now; please re-open it if you still have problems with an updated GTK. Thanks!

nandinga

2011-10-23 00:02

reporter   ~0011741

Ok. Still don't have a stable environment to test but as soon as I can get one (probably a newer distro), will try and close.

Thanks to you!!

system

2020-04-19 20:15

developer   ~0022692

Issue has been closed automatically, by Trigger Close Plugin.
Feel free to re-open with additional information if you think the issue is not resolved.

Issue History

Date Modified Username Field Change
2011-07-24 18:37 nandinga New Issue
2011-07-24 20:14 cth103 cost => 0.00
2011-07-24 20:14 cth103 Target Version => 3.0-beta1
2011-07-24 20:19 paul Note Added: 0011204
2011-07-24 20:39 nandinga Note Added: 0011205
2011-07-24 20:43 paul Note Added: 0011206
2011-07-24 21:11 nandinga Note Added: 0011208
2011-07-24 21:12 nandinga Note Added: 0011209
2011-08-11 16:29 paul Note Added: 0011297
2011-08-11 22:39 nandinga Note Added: 0011303
2011-09-20 20:05 nandinga Note Added: 0011545
2011-10-22 23:21 cth103 Note Added: 0011740
2011-10-22 23:21 cth103 Status new => resolved
2011-10-22 23:21 cth103 Resolution open => unable to reproduce
2011-10-22 23:21 cth103 Assigned To => cth103
2011-10-23 00:02 nandinga Note Added: 0011741
2020-04-19 20:15 system Note Added: 0022692
2020-04-19 20:15 system Status resolved => closed