Bug 102076 - Segmentation fault when opening a specific pdf
Summary: Segmentation fault when opening a specific pdf
Status: NEW
Alias: None
Product: poppler
Classification: Unclassified
Component: cairo backend (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: poppler-bugs
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-08-07 16:24 UTC by Thomas Keck
Modified: 2017-08-07 16:24 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
File which produces the crash (11.00 KB, application/pdf)
2017-08-07 16:24 UTC, Thomas Keck
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Keck 2017-08-07 16:24:19 UTC
Created attachment 133311 [details]
File which produces the crash

If I open the attached pdf (created by the tex file below) with evince,
I get a segmentation fault.

gdb evince:

Thread 15 "EvJobScheduler" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7f04b9ffb700 (LWP 3924114)]
0x00007f04cc3267e2 in CairoOutputDev::setSoftMask (this=0x7f0498049360, state=<optimized out>, bbox=<optimized out>, alpha=false, transferFunc=0x0, backdropColor=<optimized out>) at CairoOutputDev.cc:1801
warning: Source file is more recent than executable.
1801          cairo_pattern_set_matrix(mask, &mat);
(gdb) bt
#0  0x00007f04cc3267e2 in CairoOutputDev::setSoftMask (this=0x7f0498049360, state=<optimized out>, bbox=<optimized out>, alpha=false, transferFunc=0x0, backdropColor=<optimized out>) at CairoOutputDev.cc:1801
#1  0x00007f04b9480af3 in Gfx::doSoftMask (this=this@entry=0x7f0498050800, str=str@entry=0x7f04b9ffa520, alpha=alpha@entry=false, blendingColorSpace=blendingColorSpace@entry=0x7f049804ae60, isolated=isolated@entry=false, knockout=knockout@entry=false, transferFunc=0x0, backdropColor=0x7f04b9ffa5e0) at Gfx.cc:1418
#2  0x00007f04b94820ea in Gfx::opSetExtGState (this=0x7f0498050800, args=0x7f04b9ffa710, numArgs=<optimized out>) at Gfx.cc:1262
#3  0x00007f04b947fc2e in Gfx::go (this=this@entry=0x7f0498050800, topLevel=topLevel@entry=true) at Gfx.cc:763
#4  0x00007f04b94800d0 in Gfx::display (this=this@entry=0x7f0498050800, obj=obj@entry=0x7f04b9ffaa10, topLevel=topLevel@entry=true) at Gfx.cc:729
#5  0x00007f04b94c6215 in Page::displaySlice (this=0x7f049804a450, out=out@entry=0x7f0498049360, hDPI=hDPI@entry=72, vDPI=vDPI@entry=72, rotate=rotate@entry=0, useMediaBox=useMediaBox@entry=false, crop=crop@entry=true, sliceX=sliceX@entry=-1, sliceY=-1, sliceW=-1, sliceH=-1, printing=false, abortCheckCbk=0x0, 
    abortCheckCbkData=0x0, annotDisplayDecideCbk=0x0, annotDisplayDecideCbkData=0x0, copyXRef=false) at Page.cc:599
#6  0x00007f04cc311792 in _poppler_page_render (page=0x55b46b47ca80, cairo=0x55b46b43d610, printing=<optimized out>, print_flags=<optimized out>) at poppler-page.cc:363
#7  0x00007f04dc111401 in pdf_page_render (page=page@entry=0x55b46b47ca80, width=1709, height=2212, rc=rc@entry=0x55b46b47cac0) at ev-poppler.cc:421
#8  0x00007f04dc111641 in pdf_document_render (document=<optimized out>, rc=0x55b46b47cac0) at ev-poppler.cc:448
#9  0x00007f04ebbf8602 in ev_job_render_run (job=0x55b46b489d50) at ev-jobs.c:639
#10 0x00007f04ebbfa55a in ev_job_thread (job=0x55b46b489d50) at ev-job-scheduler.c:184
#11 ev_job_thread_proxy (data=<optimized out>) at ev-job-scheduler.c:217
#12 0x00007f04e9957bb5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#13 0x00007f04e93c86ba in start_thread (arg=0x7f04b9ffb700) at pthread_create.c:333
#14 0x00007f04e90fe3dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109
(gdb) print mask
$1 = (cairo_pattern_t *) 0x0

I'm using ubuntu 14.04
evince 3.18.2-1ubuntu
libpoppler 0.14.0ubuntu
libcairo2 1.14.6-1


Tex file:
\documentclass{article}
\usepackage{tikz}
\usetikzlibrary{fadings}

\begin{document}
  \begin{tikzpicture}
    \node[postaction={path fading=north, fading angle=-45}] {\hspace{100em}TTTTTTTTTTTTTTTTTTTTTTTTTT};
  \end{tikzpicture}
\end{document}


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.