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 521978 - [qtwrapper] Illegal CoreFoundation calls while in a forked child
[qtwrapper] Illegal CoreFoundation calls while in a forked child
Status: RESOLVED OBSOLETE
Product: GStreamer
Classification: Platform
Component: gst-plugins-bad
git master
Other Mac OS
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-03-12 10:24 UTC by Andy Wingo
Modified: 2013-08-14 05:58 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Andy Wingo 2008-03-12 10:24:55 UTC
Hello,

I installed GStreamer via MacPorts. Running gst-inspect subsequently failed:

$ gst-inspect
wingo@wingomac:~$ gst-inspect
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
[the last 2 lines repeat a bunch of times]
Error initializing: Error re-scanning registry , child terminated by signal

$ uname -a
Darwin wingomac.local 9.1.1 Darwin Kernel Version 9.1.1: Fri Dec 14 19:00:14 PST 2007; root:xnu-1228.1.30~1/RELEASE_I386 i386

Unfortunately, I was not able to debug this, as I could not get GDB to follow the fork. I worked around this issue by running gst-inspect with --gst-disable-registry-fork.
Comment 1 Daniel Macks 2008-03-12 16:30:33 UTC
Heck of a "feature" apple gave us there with 10.5, eh? See the "CoreFoundation and fork()" section of this developers' note for more info:

http://developer.apple.com/releasenotes/CoreFoundation/CoreFoundation.html
Comment 2 Andy Wingo 2008-03-12 17:40:27 UTC
Yeah, quite exciting indeed, It seems that the plugin at fault is the qtwrapper. The other plugins register fine.
Comment 3 Edward Hervey 2013-08-13 18:44:57 UTC
This bug has an assigned developer but has not received activity in almost a year.

Is the assigned person still working on this ?
Comment 4 Jan Schmidt 2013-08-13 22:40:49 UTC
This should have been fixed by the external registry helper, since there's no longer any fork w/o exec in plugin scanning.
Comment 5 Edward Hervey 2013-08-14 05:58:44 UTC
Marking as obsolete then. Nobody complained in 5 years so I'm going to say the new registry helper fixed it :)