[gstreamer-bugs] [Bug 532866] gstreamer-properties crashed with SIGSEGV in g_hash_table_lookup()

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=532866
  GStreamer | gst-plugins-good | 0.10.7

Tim-Philipp Müller <t.i.m> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEEDINFO                    |RESOLVED
                 CC|                            |t.i.m at zen.co.uk
         Resolution|                            |INCOMPLETE
   Target Milestone|HEAD                        |NONE

--- Comment #8 from Tim-Philipp Müller <t.i.m at zen.co.uk> 2010-03-16 19:18:19 UTC ---
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 at 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

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.