GNOME Bugzilla – Bug 698621
UI gets unresponsive while searching
Last modified: 2013-04-22 23:49:20 UTC
I opened a proceeding, searched by 'forge' and evince got stuck in 59%. I had tried searching with other documents of >140 pages and I could not reproduce the problem. Neither with smaller documents. I am not attaching the document because is big (1.6MB) and I am not sure about its copyright (usually these are behind a paywall). However, I found a link that would make the trick for you to reproduce the error: http://opensource.ucc.ie/icse2003/3rd-WS-on-OSS-Engineering.pdf Here is the stacktrace after I interrupted evince because it was taking too long. FWIW, the 'thread exited' appeared after evince got stuck. Starting program: /home/gpoo/code/evince/install/bin/evince [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1". [New Thread 0xb565bb40 (LWP 9097)] [New Thread 0xb4cffb40 (LWP 9098)] [New Thread 0xa737eb40 (LWP 9099)] [New Thread 0xa644fb40 (LWP 9103)] [Thread 0xb4cffb40 (LWP 9098) exited] Program received signal SIGINT, Interrupt. 0xa5a1d72b in TextBlock::visitDepthFirst (this=0x9647200, blkList=0x8687598, pos1=1988, sorted=0x9f25ad8, sortPos=2091, visited=0x9f2ea68) at TextOutputDev.cc:1851 warning: Source file is more recent than executable. 1851 for (blk3 = blkList; blk3; blk3 = blk3->next) {
+ Trace 231832
Thread 1 (Thread 0xb599aac0 (LWP 9096))
Inferior 1 [process 9096] will be killed. Quit anyway? (y or n)
Germán, the stacktrace suggests that this is a poppler bug. Did you try to reproduce using poppler-glib-demo?
it is actually a problem in poppler. Could you please forward the bug to their bugzilla?
I did not checking (I was in the middle of something else). Now I reported it and I put the stacktrace of poppler-glib-demo, although it is the same. Thanks!