GNOME Bugzilla – Bug 322054
crash on reload (ctrl-r) from pdflatex generated PDF
Last modified: 2005-11-27 12:56:05 UTC
Steps to reproduce: 1. generate a PDF using pdflatex 2. evince the generated pdf 3. hit control-r a bunch of times Stack trace: Backtrace was generated from '/home/nickm/garnome/bin/evince' (no debugging symbols found) Using host libthread_db library "/lib/tls/libthread_db.so.1". (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 1086109504 (LWP 26104)] [New Thread 1090624432 (LWP 26106)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0x0092c7a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
+ Trace 64173
Thread 1 (Thread 1086109504 (LWP 26104))
Other information: I'm using pdflatex to generate a PDF file. After regenerating, i hit control-r in the evince window to reload. Often, but not every time, it crashes --- maybe 25% of the time? In fact, I can get it to crash just by hitting control-R a few times, even if the PDF is "old". Does NOT happen with PDFs generated by epstopdf (where EPS came from openoffice-2.0). it doesn't seem to happen if I have queued control-r's (i.e. control-r while a reload is in progress) evince from garnome 2.12.1 build, gcc-3.3 -O2 -g stderr has, on launch: ** (evince:27047): WARNING **: Service registration failed. ** (evince:27047): WARNING **: No reply within specified time stderr has, on reload: (evince:27168): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
This very annoying bug impairs my usage of evince quite a bit. I'm using evince 0.4.0 under FC4. I have observed this behavior in past versions of evince also.
Actually, though, the steps to reproduce are 1. generate a PDF using pdflatex 2. evince the generated pdf 3. change the tex file 4. regenerate the PDF 5. hit control-r If it has not crashed yet, go to 3.
Grant, please check latest CVS, there were some fixes related to it.
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 314986 ***