I'd just like to note that I can reproduce this in the latest Hardy Heron on my system with 4 GB of RAM, using the Vorlesung PDF example at 400%; in fact, I don't even need to scroll. Attached is an strace log.
gwern@craft:10575~>strace -o vorlesun-evince-trace.txt evince Vorlesung_v4.pdf [ 2:41PM]
The program 'evince' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
(Details: serial 1135 error_code 11 request_code 53 minor_code 0)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
gwern@craft:10576~>evince --version [ 2:42PM]
GNOME evince 2.22.2
I'd just like to note that I can reproduce this in the latest Hardy Heron on my system with 4 GB of RAM, using the Vorlesung PDF example at 400%; in fact, I don't even need to scroll. Attached is an strace log.
gwern@craft: 10575~> strace -o vorlesun- evince- trace.txt evince Vorlesung_v4.pdf [ 2:41PM] 10576~> evince --version [ 2:42PM]
The program 'evince' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
(Details: serial 1135 error_code 11 request_code 53 minor_code 0)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
gwern@craft:
GNOME evince 2.22.2