GNOME Bugzilla – Bug 328654
evince crash with special pdf file
Last modified: 2006-12-22 06:54:06 UTC
Steps to reproduce: 1. get this pdf http://www.uni-leipzig.de/~eval/materialienunddownloads/saechshg.pdf (md5sum: 3d089986b495a907246abbb6a6cd4cc9) 2. start evince with this pdf 3. activate side pane 4. switch side pane to thumbnail view 5. quit evince 6. restart "evince saechshg.pdf" -> this crashs mostly (not every time) on most tested hosts It seems, that this bug is timing related and not always on all machines reproduceable. Stack trace: $:gdb evince (gdb) set args saechshg.pdf (gdb) run Starting program: /usr/bin/evince saechshg.pdf Reading symbols from shared object read from target memory...done. Loaded system supplied DSO at 0xffffe000 [Thread debugging using libthread_db enabled] [New Thread -1497610576 (LWP 22642)] ** (evince:22642): WARNING **: Service registration failed. ** (evince:22642): WARNING **: Unable to determine the address of the message bu s [New Thread -1498080336 (LWP 22646)] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1498080336 (LWP 22646)] 0xa76be343 in FcFontSetMatch (config=0xa6213e30, sets=0xa6b50ef8, nsets=1, p=0xa6253b80, result=0xa6b50f48) at fcmatch.c:620 620 if (cand_elts[cand_elt].object == (gdb) thread apply all bt
+ Trace 65612
Thread 1 (Thread -1497610576 (LWP 22642))
Other information: It seems, that two threads do some stuff in libfontconfig and override each other some parts of the memory. Either libfontconfig is not thread-safe or it is used somehow incorrectly.
This looks like a fontconfig problem to me, but we let the evince maintainers decide. it is a good strack trace.
*** Bug 388280 has been marked as a duplicate of this bug. ***