Bug 26784

Summary:	Broken PDF makes Evince crash
Product:	poppler	Reporter:	Charles Plessy <charles-debian-nospam>
Component:	cairo backend	Assignee:	poppler-bugs <poppler-bugs>
Status:	RESOLVED DUPLICATE	QA Contact:
Severity:	normal
Priority:	medium
Version:	unspecified
Hardware:	Other
OS:	All
URL:	http://bugs.debian.org/528467
Whiteboard:
i915 platform:		i915 features:

Description Charles Plessy 2010-02-27 01:43:05 UTC

Dear Poppler developers,

The page 6 of the following PDF file was reported on Debian to cause problems to Evince. Actually, in later versions it crashes.

http://www.bmas-conf.org/2008/5-1_Paper.pdf
http://bugs.debian.org/528467

This file also causes problems to xpdf, kpdf and gimp, but not to inkscape or imagemagick. With pdfimage, it triggers an apparently infinite loop where the sam e file is created again and again.

While it is probable that the PDF file itself is broken, I open this bug in hope it will help you to make poppler resistant to such brokenness.

Thanks a lot for your work, and have a nice week-end,

-- 
Charles Plessy
Tsurumi, Kanagawa, Japan.

Comment 1 Albert Astals Cid 2010-02-27 03:46:33 UTC

The pdfimage problem is a known problem (bug 13518)

The crash in evince has this backtrace

#0  0x00007ffff13e0576 in ?? () from /usr/lib/libpixman-1.so.0
#1  0x00007ffff13da05d in ?? () from /usr/lib/libpixman-1.so.0
#2  0x00007ffff13dec40 in ?? () from /usr/lib/libpixman-1.so.0
#3  0x00007ffff13de89b in pixman_image_composite () from /usr/lib/libpixman-1.so.0
#4  0x00007ffff656efa8 in ?? () from /usr/lib/libcairo.so.2
#5  0x00007ffff6583bbd in ?? () from /usr/lib/libcairo.so.2
#6  0x00007ffff65853bb in ?? () from /usr/lib/libcairo.so.2
#7  0x00007ffff6585e9b in ?? () from /usr/lib/libcairo.so.2
#8  0x00007ffff6586312 in ?? () from /usr/lib/libcairo.so.2
#9  0x00007ffff6582b8f in ?? () from /usr/lib/libcairo.so.2
#10 0x00007ffff656b5aa in ?? () from /usr/lib/libcairo.so.2
#11 0x00007ffff6566170 in cairo_fill_preserve () from /usr/lib/libcairo.so.2
#12 0x00007ffff6566189 in cairo_fill () from /usr/lib/libcairo.so.2
#13 0x00007ffff7bcd166 in CairoOutputDev::tilingPatternFill (this=0x69fc60, state=0x89cf00, str=<value optimized out>, paintType=<value optimized out>,
    resDict=<value optimized out>, mat=0x7fffffffc720, bbox=0x95ec28, x0=1976, y0=-1, x1=5025, y1=906, xStep=<value optimized out>, yStep=<value optimized out>)
    at /home/tsdgeos/cvs/poppler/poppler/CairoOutputDev.cc:753
#14 0x00007ffff4d7f283 in Gfx::doTilingPatternFill (this=0x873800, tPat=0x95ec10, stroke=<value optimized out>, eoFill=<value optimized out>)
    at /home/tsdgeos/cvs/poppler/poppler/Gfx.cc:2054

Changing the subject to cover only the cairo problem since the other one is already well documented

Comment 2 Carlos Garcia Campos 2010-03-01 01:39:29 UTC

It doesn't crash for me

Comment 3 Søren Sandmann Pedersen 2010-03-01 02:19:06 UTC

It crashes for me, with cairo 1.9.2 and pixman git master. What happens is that cairo makes a 0x0 image and then tries to composite with it.

I believe this is a bug in cairo, as discussed in bug 24693.

I'll probably add a return_if_fail() to pixman to warn about this.

Comment 4 Carlos Garcia Campos 2010-03-01 02:30:08 UTC

Marking a duplicate then, thanks Søren. 

*** This bug has been marked as a duplicate of bug 24693 ***

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.