After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 308005 - Crashing when tryin to reach End of Document
Crashing when tryin to reach End of Document
Status: RESOLVED NOTGNOME
Product: evince
Classification: Core
Component: general
0.3.x
Other other
: Normal normal
: ---
Assigned To: Evince Maintainers
Evince Maintainers
Depends on:
Blocks:
 
 
Reported: 2005-06-17 01:41 UTC by masterloki0
Modified: 2005-07-08 10:55 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10



Description masterloki0 2005-06-17 01:41:02 UTC
Distribution: Fedora Core release 4 (Stentz)
Package: evince
Severity: normal
Version: GNOME2.10.0 0.3.x
Gnome-Distributor: Red Hat, Inc
Synopsis: Crashing when tryin to reach End of Document
Bugzilla-Product: evince
Bugzilla-Component: general
Bugzilla-Version: 0.3.x
BugBuddy-GnomeVersion: 2.0 (2.10.0)
Description:
Description of the crash:  
   The app crashed when I try to reach to end of the document

Steps to reproduce the crash:
1.  Open any Web Browser
2.  Go to http://www.ostg.com/bcg/BCGHACKERSURVEY-0.73.pdf
3.  Scroll down and watch

Expected Results:
    The app will crash


How often does this happen?
   Each time I read this document

Additional Information:
   None



Debugging Information:

Backtrace was generated from '/usr/bin/evince'

(no debugging symbols found)
Using host libthread_db library "/lib/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)
[Thread debugging using libthread_db enabled]
[New Thread -1208506688 (LWP 4938)]
[New Thread -1210803280 (LWP 4939)]
(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)
(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)
0x00ce8402 in ?? ()

Thread 2 (Thread -1210803280 (LWP 4939))

  • #0 ??
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 SplashXPathScanner::SplashXPathScanner
    from /usr/lib/libpoppler.so.0
  • #5 Splash::fillWithPattern
    from /usr/lib/libpoppler.so.0
  • #6 Splash::fill
    from /usr/lib/libpoppler.so.0
  • #7 SplashOutputDev::eoFill
    from /usr/lib/libpoppler.so.0
  • #8 Gfx::opEOFill
    from /usr/lib/libpoppler.so.0
  • #9 Gfx::execOp
    from /usr/lib/libpoppler.so.0
  • #10 Gfx::go
    from /usr/lib/libpoppler.so.0
  • #11 Gfx::display
    from /usr/lib/libpoppler.so.0
  • #12 Page::displaySlice
    from /usr/lib/libpoppler.so.0
  • #13 poppler_page_render_to_pixbuf
    from /usr/lib/libpoppler-glib.so.0
  • #14 pdf_document_get_type
  • #15 ev_document_thumbnails_get_thumbnail
  • #16 ev_job_thumbnail_run
  • #17 ev_document_find_changed
  • #18 g_static_private_free
    from /usr/lib/libglib-2.0.so.0
  • #19 start_thread
    from /lib/libpthread.so.0
  • #20 clone
    from /lib/libc.so.6




------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-06-17 01:41 UTC -------


The original reporter of this bug does not have
   an account here. Reassigning to the person who moved
   it here, unknown@bugzilla.gnome.org.
   Previous reporter was masterloki0@gmail.com.

Comment 1 Marco Pesenti Gritti 2005-06-17 10:09:24 UTC
Hi, this looks like a bug with the PDF backend.  Could you please follow these
instructions to help get this 
 bug fixed.  Thank You. http://live.gnome.org/Evince/PopplerBugs#poppler
 
Comment 2 Michaël Arnauts 2005-06-18 14:29:19 UTC
No crash here, however, as soon as I reach page 36, i get a 100% CPU, and a
blank page for about 20 seconds, after that, the graphic is shown.

I have to wait for page 36 to be fully rendered, because if I continiue
scrolling or clicking next, all the pages will be white (even the ones before 36).
Comment 3 Marco Pesenti Gritti 2005-07-08 10:55:10 UTC
https://bugs.freedesktop.org/show_bug.cgi?id=3728