[gstreamer-bugs] [Bug 520468] Add a Env to enable/disable scan_and_update_registry for usage on embedded
GStreamer (bugzilla.gnome.org)
bugzilla-daemon at bugzilla.gnome.org
Fri Apr 25 17:27:09 PDT 2008
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=520468
GStreamer | gstreamer (core) | Ver: 0.10.17
------- Comment #39 from Jan Schmidt 2008-04-26 00:27 UTC -------
Try to put all of gst_init() in a background thread sounds painful to me - but
possible, and without changing GStreamer itself.... just all the applications,
heh.
An approach I've thought of before would be to make gst_init() spawn a thread
for registry reading and instrumenting all the entry points to the
gst_registry_* with a _priv_gst_registry_wait_loaded()... so that the registry
loading occurs asynchronously and the program can continue without blocking
until the first time it actually tries to look at plugin features or create an
element.
It doesn't work if anything accesses the GstRegistry stuff directly though -
everyone would need to go through the API
--
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=520468.
More information about the Gstreamer-bugs
mailing list