[poppler] [gs-devel] Bad interaction between libgs, lcms2 and poppler
Ken Sharp
ken.sharp at artifex.com
Mon Jan 13 13:20:12 PST 2014
At 22:07 13/01/2014 +0100, Albert Astals Cid wrote:
>The only solution I can think of from my side is never unloading the plugin
>that uses libgs, but I'd like not to get there.
>
>I looked at lcms code and doesn't seem to be a way for libgs to unload it's
>plugin (there seems to be a unloadAll, but that would not be a good idea
>either).
>
>Do you think it makes sense for lcms to provide such a functionality?
>
>Or anyone has a better idea?
We are currently in discussion with Marti, the LCMS developer, to deal (I
think) with this problem. We are looking more generally at thread safety
and LCMS but I believe that this is a particular instance of the problems
we have seen.
Of course this will mean that we depend on a new release of LCMS, and then
of Ghostscript, at the very least so I'm afraid that I don't see a solution
to this at the present.
I'm not close to the problem myself, so I'm CC'ing this to Robin (I'm not
sure he sees gs-devel) in case he would like to add something.
Ken
More information about the poppler
mailing list