GNOME Bugzilla – Bug 386847
crash in Volume Control: Surfing the net - visiti...
Last modified: 2007-01-08 22:43:07 UTC
What were you doing when the application crashed? Surfing the net - visiting Orkut Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 34680832 vsize: 0 resident: 34680832 share: 0 rss: 4870144 rss_rlim: 0 CPU usage: start_time: 1166375524 rtime: 0 utime: 0 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/libexec/mixer_applet2' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1226052848 (LWP 7274)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 94889
Thread 1 (Thread -1226052848 (LWP 7274))
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
I have installed dbg packages as suggested to add debugging info, but the apps are not crashing! I mean - the crash is not reproducible so I cannot generate the better stack trace. However, this will be useful for the next time it occurs. Thanks.
In particular, please have these two packages installed: sudo apt-get install libglib2.0-0-dbg libgstreamer0.10-0-dbg If you know how to do this, you could try the following (someone mentioned it only happens when users log in for the first time, but I haven't been able to reproduce this myself yet): - log out from your desktop environment (GNOME presumably) - switch to a text console and log in as a normal user (CTRL+ALT+F1 usually) - do rm -rf ~/.gstreamer-0.10 - switch back to your login manager (CTRL+ALT+F7 usually) - log in and see if the crash happens again
I'd already installed those two when I installed dbg packages. Regarding your second suggestion, there is no crash. I played mp3 files even, after finishing the procedure.
*** Bug 362311 has been marked as a duplicate of this bug. ***
> Regarding your second suggestion, there is no crash. I played mp3 > files even, after finishing the procedure. Shame, thanks for trying. No idea what the problem is then. The stack trace would seem to indicate a problem in GLib's GSLice allocator to me then (all our calls to g_object_new() in gstregistryxml are without additional properties, so it can't be that we're passing wrong args there). Hard to say without a better stack trace or a way to reproduce. There is a whole bunch of similar bugs, all of which are crashes in g_slice_alloc() from g_type_create_instance(); many of those seem to be from other panel applets as well. Couldn't find any bugs in GLib that match this issue though, so chances are fairly good that this is due to some memory corruption caused shortly before and throwing off the GLib allocator. Even more so since I don't see how gst_registry_xml_write_cache() would cause a new object to be created. Possibly related: - bug #379690: crash in g_free()/free() from gst_registry_xml_write_cache() - bug #354483: crash in xmlTextReaderRead() (!!!) from gst_registry_xml_write_cache()
*** Bug 379379 has been marked as a duplicate of this bug. ***
Another variation: - bug #375085: trace with gst_type_find_factory_get_list(), g_type_class_ref(), and g_type_instance_create() from gst_registry_xml_write_cache()
Probably due to late g_thread_init(), see bug #391278. Closing until someone can reproduce a core >= current CVS (if it's still a problem I'm sure someone will, probably sooner rather than later). *** This bug has been marked as a duplicate of 391278 ***