[gstreamer-bugs] [Bug 348918] New: application should decide whether or not to use fork() to read registry cache

[GStreamer (bugzilla.gnome.org)]

Do not reply to this via email (we are currently unable to handle email
responses and they get discarded).  You can add comments to this bug at
http://bugzilla.gnome.org/show_bug.cgi?id=348918
 GStreamer | gstreamer (core) | Ver: 0.10.9

           Summary: application should decide whether or not to use fork()
                    to read registry cache
           Product: GStreamer
           Version: 0.10.9
          Platform: Other
        OS/Version: All
            Status: UNCONFIRMED
          Severity: enhancement
          Priority: Normal
         Component: gstreamer (core)
        AssignedTo: gstreamer-bugs at lists.sourceforge.net
        ReportedBy: martti.mela at iki.fi
         QAContact: gstreamer-bugs at lists.sourceforge.net
     GNOME version: Unversioned Enhancement
   GNOME milestone: Unspecified


Current versions of gst don't let application to initialize gst without fork()
if gst is compiled with HAVE_FORK enabled. This causes a serious problem if gst
is initialized in a dynamic extension (i.e. plugin), not in the main()
function. Current behaviour of gst_init() (when HAVE_FORK enabled) copies the
whole process and causes gst_init() to fail when called in a plugin (or
extension), not in the main() of the application.

Calling application should be able to initialize gst also without fork(). In
some cases it's not possible to do gst_init() in the main(); this wouls cause
the main application to be dependent of gst.


-- 
Configure bugmail: http://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.