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 543045 - Evince has effectively crashes when opening this file.
Evince has effectively crashes when opening this file.
Status: RESOLVED DUPLICATE of bug 523372
Product: evince
Classification: Core
Component: PDF
2.22.x
Other All
: High critical
: ---
Assigned To: Evince Maintainers
Evince Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-07-15 07:25 UTC by Paul Rawson
Modified: 2009-11-02 09:45 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description Paul Rawson 2008-07-15 07:25:21 UTC
Steps to reproduce:
1. Open file.
2. System will die in less than a second, unless you have a lot of swap, which may give you time to switch to a terminal and kill evince.


Stack trace:


Other information:
Evince opened this file before, but crashed while I was viewing it. Now as soon as the file is opened, evince freezes, consuming all system memory almost instantly.
Comment 1 Paul Rawson 2008-07-15 07:30:41 UTC
Sorry, it looks like the file is about 200K too big to attach. If anyone wants it, I can email. Don't worry, it's just a pdf.
Comment 2 Reinout van Schouwen 2008-07-15 13:58:47 UTC
Thanks for taking the time to report this bug.
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 3 Paul Rawson 2008-07-16 02:09:14 UTC
The program didn't really "crash," it just went haywire, hogging all memory.And anyway, this problem is reproducible after a reboot, though this time it didn't consume all memory, just 2GB RAM and 500MB swap.Since evince does not crash entirely anymore, I've had a chance to play with it, and it looks like this problem occurs when zooming. Memory usage at 100% zoom: 501MB, at 150% zoom: dancing between 700 and 750MB, then drops down to 620MB.300% puts me at 1.5GB used RAM and 400% uses the aforementioned 2GB RAM and 500MB swap. Hope this helps narrow down the problem. Again, I have the file that causes this if anyone wants a copy. (It's public domain too)
-Paul
Comment 4 Carlos Garcia Campos 2008-07-20 11:03:09 UTC
Does this happen with a document containing scanned images or just big images? It could be a duplicated of bug #504913. 

Thanks. 
Comment 5 Paul Rawson 2008-07-21 00:49:48 UTC
I don't know. The file is a map of a city with zoning information. I guess it's some sort of vector graphic since when you zoom in (in adobe which doesn't crash) lines will be jagged for a second, then will smooth out. If that's not what you're looking for, let me know (and how) and I'll get the info you need.
Comment 6 Alexander Kojevnikov 2009-04-28 14:22:57 UTC
(In reply to comment #5)
> I don't know. The file is a map of a city with zoning information. I guess it's
> some sort of vector graphic since when you zoom in (in adobe which doesn't
> crash) lines will be jagged for a second, then will smooth out. If that's not
> what you're looking for, let me know (and how) and I'll get the info you need.
> 

Does it have a huge page size? If that's the case, it's a duplicate of bug 478801.
Comment 7 Emmanuel Fleury 2009-11-02 09:45:26 UTC

*** This bug has been marked as a duplicate of bug 523372 ***