Evince crashes due to unable to allocate memory for image

Bug #240044 reported by gwern
4
Affects Status Importance Assigned to Milestone
poppler (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Binary package hint: evince

gwern@craft:10580~>uname -a [ 2:49PM]
Linux craft 2.6.24-19-generic #1 SMP Wed Jun 4 15:10:52 UTC 2008 x86_64 GNU/Linux
gwern@craft:10581~>evince --version [ 2:49PM]
GNOME evince 2.22.2
gwern@craft:10582~>lsb_release -rd [ 2:49PM]
Description: Ubuntu 8.04.1
Release: 8.04
gwern@craft:10583~>apt-cache policy evince [ 2:49PM]
evince:
  Installed: 2.22.2-0ubuntu1
  Candidate: 2.22.2-0ubuntu1
  Version table:
 *** 2.22.2-0ubuntu1 0
        500 http://archive.ubuntu.com hardy-updates/main Packages
        100 /var/lib/dpkg/status
     2.22.1.1-0ubuntu1 0
        500 http://archive.ubuntu.com hardy/main Packages

gwern@craft:10569~>strace -o evince-trace.txt evince causality.pdf [ 2:27PM]
/usr/share/themes/Glider/gtk-2.0/gtkrc:29: Invalid symbolic color 'fg_color'
/usr/share/themes/Glider/gtk-2.0/gtkrc:29: error: invalid identifier `fg_color', expected valid identifier
Error: Unable to allocate memory for image.
Error: Unable to allocate memory for image.

Evince crashes quickly with that error. causality.pdf is 328K and my machine has 4 gigs of RAM. I don't *think* this is a duplicate with any other bug reports, but I could be wrong as many deal with evince crashes. The specific PDF comes from http://arxiv.org/abs/0709.4443v2

(I renamed it, but they're the same file:
gwern@craft:10593~>md5sum 0709.4443v2 causality.pdf [ 2:53PM]
0e7be7af9c588546449471d783f5bb7d 0709.4443v2
0e7be7af9c588546449471d783f5bb7d causality.pdf
)

Revision history for this message
gwern (gwern0) wrote :
Revision history for this message
Marcel Stimberg (marcelstimberg) wrote :

The mentioned pdf crashes my evince as well, although with a segmentation fault. After that evince complains "Your computer does not have enough free memory to automatically analyze the problem and send a report to the developers." The backtrace points to poppler, therefore I reassigned the bug. I think it is the same as Bug #188079 (which expired but is still present), therefore I mark this bug as duplicate. Nevertheless, I'll attach my backtrace.
My configuration:
mst@lifecompi:~$ uname -a
Linux lifecompi 2.6.24-19-generic #1 SMP Wed Jun 4 16:35:01 UTC 2008 i686 GNU/Linux
mst@lifecompi:~$ apt-show-versions evince
evince/hardy uptodate 2.22.2-0ubuntu1
mst@lifecompi:~$ apt-show-versions libcairo2
libcairo2/hardy uptodate 1.6.0-0ubuntu2
mst@lifecompi:~$ apt-show-versions libpoppler2
libpoppler2/hardy uptodate 0.6.4-1ubuntu1

Changed in evince:
status: New → Confirmed
Revision history for this message
Marcel Stimberg (marcelstimberg) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.