[gstreamer-bugs] [Bug 584291] Cannot create elements after calling gst_update_registry

[GStreamer (bugzilla.gnome.org)]

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=584291

  GStreamer | gst-ffmpeg | Ver: git

Wim Taymans changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
 Attachment #135619|none                        |committed
               Flag|                            |
             Status|ASSIGNED                    |RESOLVED
         Resolution|                            |FIXED
   Target Milestone|HEAD                        |0.10.8




------- Comment #3 from Wim Taymans  2009-06-05 11:21 UTC -------
commit cfbb046f1e73e5b27c3436120660f27bacc7d6c4
Author: Jordi Mas <jordimash at gmail.com>
Date:   Fri Jun 5 13:19:03 2009 +0200

    ffmpeg: make elements reusable after registry rescan

    If the same instance of the plugin is asked to be initialised more that
once,
    instances after the first one do not register the elements properly and the
    elements become not usable.

    For example, if you call gst_update_registry (), is not possible to create
    elements after the call since the plugin is asked to be initialised again
and
    does not register the elements.

    Fixes #584291

commit 6d643a134e88c2cff1672bd1e72ebcb0dbe8b969
Author: Wim Taymans <wim.taymans at collabora.co.uk>
Date:   Fri Jun 5 13:17:09 2009 +0200

    check: add registry rescan test


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=584291.