GNOME Bugzilla – Bug 684989
Evince Crashes When Viewing Parts of PDF
Last modified: 2012-11-02 13:57:42 UTC
When viewing the PDF I get the following error upon scrolling to about page 32. evince: GfxState.cc:4159: void GfxGouraudTriangleShading::getTriangle(int, double*, double*, GfxColor*, double*, double*, GfxColor*, double*, double*, GfxColor*): Assertion `!isParameterized()' failed. Aborted Similarly `evince -i 32 $pdf` crashes as well.
The file upload failed (silently) because the file is too large. You can find it here: http://www.engsoc.org/~kevincox/f/Lecture%203%20-%20Engineering%20Reporting%20&%20Units0-3.pdf.
Could you tell which version of poppler are you using? The assertion you are getting is from poppler, and most probably this is either a poppler bug or a weird pdf file. In my fedora 17 machine, I don't get the crash
poppler 0.20.3-1
Neither I can. The only problem I see is the second column in page 5, which renders ugly (a poppler issue, probably). I noticed that getting the page 32 is slightly slower than the other pages, but it renders fine in my machine, as well as the rest of the document. The PDF does not look like big, except if there were memory constraints. What are your machine settings? Can you reproduce it in a different machine?
This file makes my evince crash as well. Backtrace is generated at <https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1059837>. libpoppler28 0.20.4-0ubuntu1 evince-common 3.6.0-0ubuntu1
> The PDF does not look like big, except if there were memory constraints. I have 4GB of ram and am not doing much. > What are your machine settings? What exactly do you mean? > Can you reproduce it in a different machine? I crashes on my other arch computer as well. (Only 1GB ram and 32-bit).
I have 8GB of RAM which are mostly empty. This is a 64bit system. I am using Ubuntu 12.10. So this is not depending on the architecture. And it does happen on Ubuntu and some other distribution of Kevin. Kevin, which distribution are you running?
This is a duplicate of bug #684151 I think
(In reply to comment #6) > > The PDF does not look like big, except if there were memory constraints. > > I have 4GB of ram and am not doing much. > > > What are your machine settings? > > What exactly do you mean? Architecture (it seems 64bits), distro version, package versions, etc. Also, having a backtrace would help to determine where is the problem. For that, you have to install the debugging symbols (usually, the same package name plus the prefix '-dbg'). More information on how to get backtraces: https://live.gnome.org/GettingTraces/DistroSpecificInstructions
I'm away from the computer right now but both are arch Linux reasonably up to date (within a week, I'll update and check again). One is 32 and one is 64 bit.
(In reply to comment #5) > This file makes my evince crash as well. > > Backtrace is generated at > <https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1059837>. > > libpoppler28 0.20.4-0ubuntu1 > evince-common 3.6.0-0ubuntu1 The stacktraces in that bug report do not have symbols. Can you install the debug symbols and try again? https://live.gnome.org/GettingTraces/DistroSpecificInstructions
What symbols are missing in <https://launchpadlibrarian.net/118046342/Stacktrace.txt>? Looks detailed to me.
Created attachment 225548 [details] Stack Trace
This is poppler bug https://bugs.freedesktop.org/show_bug.cgi?id=56463, which has just been fixed.