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 591354 - The application suddenly closes whenever i try to open a 12 MB pdf book
The application suddenly closes whenever i try to open a 12 MB pdf book
Status: RESOLVED DUPLICATE of bug 415714
Product: evince
Classification: Core
Component: PDF
2.22.x
Other Linux
: High critical
: ---
Assigned To: Evince Maintainers
Evince Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-08-10 18:15 UTC by Azhaguselvan
Modified: 2009-11-15 11:29 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Attachments
Stack trace for the bug (2.63 KB, application/octet-stream)
2009-11-15 03:13 UTC, Azhaguselvan
Details

Description Azhaguselvan 2009-08-10 18:15:28 UTC
Steps to reproduce:
1. Try to open a large size say 12 MB book(which i used) in evince
2. The evine will close immediatly.
3. 


Stack trace:


Other information:
Comment 1 Fabio Durán Verdugo 2009-08-10 18:46:20 UTC
Thanks for taking the time to report this bug.
This bug report isn't very useful because it doesn't describe the bug well. If you have time and can still reproduce the bug, please read http://bugzilla.gnome.org/bug-HOWTO.html and add a more useful description to this bug.
Comment 2 Emmanuel Fleury 2009-11-14 19:44:37 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.

Thanks!
Comment 3 Azhaguselvan 2009-11-15 02:05:42 UTC
Steps to reproduce:
1. Try to open a large size say 12 MB book(i used Wiley Ruby on Rails Bible) in evince
2. The evine will close immediatly. 

But I tried with some other files even a 19 MB one. There are no crashes

Stack trace:


Other information:

Actual results: 
 The application closed suddenly without any warnings/errors

Expected results:
  The application shouldn't have closed - it should open the book.

Version:
   Evince Document Viewer 2.22.2

Platform

   Debain GNU/Linux 5.0.3
Comment 4 Fabio Durán Verdugo 2009-11-15 02:17:20 UTC
you can public a link to download file?

and can you try with a newer evince version?, can you reproduce?, thank for you reply,

and you can send the stack trace, because, without a stack trace from the crash it's very hard to determine what caused it.
Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Comment 5 Azhaguselvan 2009-11-15 03:13:17 UTC
Created attachment 147753 [details]
Stack trace for the bug

Stack trace for the bug
Comment 6 Azhaguselvan 2009-11-15 03:14:35 UTC
I have attached the stack trace! Please let me know if i have to give additional details :)
Comment 7 Emmanuel Fleury 2009-11-15 08:59:06 UTC
Thanks a lot for your report. I think you should just copy the stack inside the body of the message like this :) :

debian-desktop:/home/selva# gdb evince
GNU gdb 6.8-debian
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i486-linux-gnu"...
(gdb) set pagination 0
(gdb) run /home/selva/Desktop/clutters/Wiley.Ruby.on.Rails.Bible.Oct.2008.pdf 
Starting program: /usr/bin/evince /home/selva/Desktop/clutters/Wiley.Ruby.on.Rails.Bible.Oct.2008.pdf
[Thread debugging using libthread_db enabled]
[New Thread 0xb6adc700 (LWP 6566)]

(evince:6566): GnomeUI-WARNING **: While connecting to session manager:
Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed.

** (evince:6566): WARNING **: Service registration failed.

** (evince:6566): WARNING **: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
[New Thread 0xb6981b90 (LWP 6578)]

Program received signal SIGSEGV, Segmentation fault.

Thread 3064841984 (LWP 6566)

  • #0 Catalog::embeddedFile
    from /usr/lib/libpoppler.so.3
  • #1 poppler_document_get_attachments
    from /usr/lib/libpoppler-glib.so.3
  • #2 pdf_document_get_attachments
    at /build/buildd/evince-2.22.2/./backend/pdf/ev-poppler.cc line 421
  • #3 ev_document_get_attachments
    at /build/buildd/evince-2.22.2/./libdocument/ev-document.c line 206
  • #4 ev_sidebar_attachments_set_document
    at /build/buildd/evince-2.22.2/./shell/ev-sidebar-attachments.c line 636
  • #5 ev_sidebar_set_document
    at /build/buildd/evince-2.22.2/./shell/ev-sidebar.c line 511
  • #6 ev_window_setup_document
    at /build/buildd/evince-2.22.2/./shell/ev-window.c line 1126
  • #7 ??
    from /usr/lib/libglib-2.0.so.0
  • #8 ??
  • #9 ??
  • #10 ??
  • #11 ??
    from /usr/lib/libglib-2.0.so.0
  • #12 ??
    from /lib/i686/cmov/libpthread.so.0
  • #13 ??
    from /usr/lib/libglib-2.0.so.0
  • #14 ??
  • #15 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0

It helps the triaging of the bug. ;)
Comment 8 Emmanuel Fleury 2009-11-15 09:03:47 UTC
Thanks again for the bug report. However, 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 bug 415714 ***
Comment 9 Azhaguselvan 2009-11-15 11:10:11 UTC

>Thanks a lot for your report. I think you should just copy the stack inside the
>body of the message like this :) :

Sorry. I am a newbie learning things. Will take care on my next bug report :)


>It helps the triaging of the bug. ;)

Glad that i could make it :)
Comment 10 Emmanuel Fleury 2009-11-15 11:29:50 UTC
> Sorry. I am a newbie learning things. Will take care on my next bug report :)

It's absolutely no problem. Everybody need to learn. Keep going on helping to triage bugs, it helps a lot. 

Thanks. :)