Cannot get gimp app running

Jeremy Huddleston Sequoia jeremyhu at
Mon Nov 3 11:14:58 PST 2014

FWIW, the issue is that p11-kit (a dependency of the ffmpeg gegl module) is adding a child atfork handler when the ffmpeg gegl module is opened during initialization.  When the module is closed after reading in initialization iformation, the system is left with a dangling pointer.  gimp later fork()s to execute some child processes

This bug shows off exactly why dlclose() is so dangerous and why fork()/exec() is so bad.  Don't dlclose(); our VM is quite large these days.  Don't fork()/exec() as it wastes cycles and is prone to this kind of bug; use posix_spawn APIs instead.  They're MUCH more efficient.

I added a patch to which just disables the dlclose() in gmodule.


> On Nov 2, 2014, at 09:38, Eric A. Borisch <eborisch at> wrote:
> On Sat, Nov 1, 2014 at 8:07 PM, Gregory Seidman <gsslist+macports at> wrote:
> This is a known, upstream bug:
> --Greg
> On Sat, Nov 01, 2014 at 06:45:55PM -0500, Eric A. Borisch wrote:
>> Are you able to open something that uses a plugin, like a png? My gimp
>> starts up, but none of the plugins (required for most file types) are
>> working.
>> - Eric
> I am aware. I was trying to determine if David's was somehow working (including plugins.) Turns out it was not (same boat everyone else is in.)
> - Eric
> _______________________________________________
> macports-users mailing list
> macports-users at

More information about the macports-users mailing list