After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 350879 - [init] Mark gstreamer as being initialized during registry scanning.
[init] Mark gstreamer as being initialized during registry scanning.
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: gstreamer (core)
git master
Other Linux
: Normal normal
: 0.10.10
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-08-11 12:40 UTC by Edward Hervey
Modified: 2006-08-11 15:08 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Patch to set core as initialized before registry scanning (1.08 KB, patch)
2006-08-11 12:42 UTC, Edward Hervey 		committed Details | Review

Description Edward Hervey 2006-08-11 12:40:53 UTC 
During GStreamer initialization, GStreamer should be considered as initialized when doing the registry scanning/updating because:
_ it isn't really part of the initialization (gstreamer is ready to be used, except for the plugins. All the core API can be used).
_ if a plugin, for one reason or another, calls gst_init() it will initialize GStreamer again.

Attached is a proposed patch to fix that behaviour.
Comment 1 Edward Hervey 2006-08-11 12:42:20 UTC 
Created attachment 70708 [details] [review]
Patch to set core as initialized before registry scanning
Comment 2 Edward Hervey 2006-08-11 15:08:24 UTC 
Approved by lord Wim Taymans of the order of the Holy Hackers !

2006-08-11  Edward Hervey  <edward@fluendo.com>

	* gst/gst.c: (gst_init_check), (init_post):
	Set gst as being initialized before scanning/updating the registry,
	since there might be some plugins that call gst_init() and we don't
	want to loop back in.
	Closes #350879