GNOME Bugzilla – Bug 532866
gstreamer-properties crashed with SIGSEGV in g_hash_table_lookup()
Last modified: 2010-03-16 19:18:19 UTC
this bug has been filed here: https://bugs.edge.launchpad.net/ubuntu/+source/gnome-media/+bug/199577 "gstreamer-properties crashes when testing the video device: $ gstreamer-properties gstreamer-properties-Message: Skipping unavailable plugin 'artsdsink' gstreamer-properties-Message: Skipping unavailable plugin 'sdlvideosink' gstreamer-properties-Message: Skipping unavailable plugin 'v4lmjpegsrc' gstreamer-properties-Message: Skipping unavailable plugin 'qcamsrc' gstreamer-properties-Message: Skipping unavailable plugin 'esdmon' Segmentation fault (core dumped)" ".
+ Trace 197581
Thread 1 (process 9968)
gstreamer? I don't know..
I'm experiencing very similar behavior to this bug. gstreamer-properties crashes on my system (Ubuntu 8.04 amd64) when clicking the "Test" button for input video. The program will also seg fault if the "Plugin:" field for input video is selected. The relevant debugging information from gdb is as follows: gstreamer-properties-Message: Skipping unavailable plugin 'esdmon' [New Thread 0x41006950 (LWP 9314)] [Thread 0x41006950 (LWP 9314) exited] (no debugging symbols found) (no debugging symbols found) [New Thread 0x41006950 (LWP 9315)] [Thread 0x41006950 (LWP 9315) exited] [New Thread 0x41006950 (LWP 9316)] [Thread 0x41006950 (LWP 9316) exited] *PRESS "TEST" BUTTON* Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7f0bbaebb7a0 (LWP 9301)] 0x00007f0bb77da8cd in gst_plugin_feature_type_name_filter () from /usr/lib/libgstreamer-0.10.so.0 (gdb) Quit
Looks like a v4lsrc bug again
This bug is going to require someone with a crashing system to provide more info. We need a full stack trace of all threads on a gstreamer install with full debug symbols enabled. Can someone of the original reports provide this info?
I'm asking on the downstream report. hope to have news soon. Thanks Wim.
Pedro, any updates on this ?
no news so far, no reporters reply to my last comment on the ubuntu report... feel free to close it if the bug is no use for you folks. Thanks in advance!.
Not quite sure what to do this with the information avilable. This *might* be fixed by this commit, for what it's worth: commit 8fe63000de31bb2bcf346d59230dea06117997cd Author: Benjamin Otte <otte@redhat.com> Date: Fri Mar 12 16:42:47 2010 +0100 plugins: Do not ever unload a plugin after calling into it This is what can happen in a plugin_init function: - An element based on GstBaseSink is registered - Other elements fail to register - The plugin_init function returns FALSE Now if this the plugin is the first plugin to link against libgstbase.so, it will have caused libgstbase.so to be loaded and static strings from that library will have been added to gobject while registering GstBaseSink. So unloading the plugin will cause those strings to go stale and the next plugin using GstBaseSink will crash. So we must not unload modules after calling into them ever. https://bugzilla.redhat.com/show_bug.cgi?id=572800