Red Hat Bugzilla – Bug 977528
[abrt] evince-3.8.2-1.fc19: gs_lcms2_malloc: Process /usr/bin/evince was killed by signal 11 (SIGSEGV)
Last modified: 2015-02-17 10:40:49 EST
Description of problem:
I opened a PDF file which had accidentally the file extension *.ps. After renaming the PDF file to *.pdf, evince does not crash again.
Version-Release number of selected component:
cmdline: evince output.ps
runlevel: N 5
var_log_messages: Jun 24 21:26:57 banach abrt: Saved core dump of pid 5474 (/usr/bin/evince) to /var/tmp/abrt/ccpp-2013-06-24-21:26:56-5474 (143441920 bytes)
Thread no. 1 (10 frames)
#0 gs_lcms2_malloc at base/gsicc_lcms2.c:48
#1 _cmsMallocZeroDefaultFn at cmserr.c:97
#2 AllocateToneCurveStruct at cmsgamma.c:165
#3 cmsBuildSegmentedToneCurve at cmsgamma.c:582
#4 cmsBuildParametricToneCurve at cmsgamma.c:655
#5 Build_sRGBGamma at cmsvirt.c:620
#6 cmsCreate_sRGBProfileTHR at cmsvirt.c:636
#7 GfxColorSpace::setupColorProfiles at GfxState.cc:412
#8 Gfx::Gfx at Gfx.cc:558
#9 Page::createGfx at Page.cc:489
Created attachment 764760 [details]
Created attachment 764761 [details]
Created attachment 764762 [details]
Created attachment 764763 [details]
Created attachment 764764 [details]
Created attachment 764765 [details]
Created attachment 764766 [details]
Created attachment 764767 [details]
Created attachment 764768 [details]
*** Bug 957325 has been marked as a duplicate of this bug. ***
This looks like a problem in lcms2 => I'm reassigning this bug to it.
My theory about this is that lcms2 ends up getting used from two different objects in the same process.
poppler is one of them, libgs is the other (I'm not sure what brings it in).
When libgs is initialized it sets the memory management functions and decides what context to give them.
When poppler later tries to use a function from the non-THR API, a NULL context is given but the memory management functions from libgs are still used.
*** Bug 987592 has been marked as a duplicate of this bug. ***
Attempt to open postscript file
cmdline: evince /home/paul/Desktop/test.ps
reason: Process /usr/bin/evince was killed by signal 11 (SIGSEGV)
runlevel: N 5
*** Bug 1039673 has been marked as a duplicate of this bug. ***
What's the status of this? Is it fixed in any version of Fedora? Fixed upstream?
(In reply to Tim Waugh from comment #16)
> Fixed upstream?
Yes, the lcms 2.6 work introduced a "context" that makes it possible to use lcms2 from two different libraries. I don't know the gs version required to use this new feature tho, but they were the ones to contribute the code to lcms2...
This message is a notice that Fedora 19 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 19. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 19 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.