Please describe the problem:
Once I opened a .pdf and wanted to zoom in (300%) the application Blocks my whole Desktop or more precisely after long time of waiting for my pc to switch programm I can stop it by killing the process. Once I let the PC run on its own and was afk  for about 45 minutes the terminal said something about evince receiving a X-Windows error. I pasted completely error-report in the more information box. And since it crashed the first time its impossible to open a document ( I tried some .pdf s and once a printing preview out of kpdf) because on every lunch of document it wants to scale it to 300% but block. After some minutes the system monitor showed me that evince uses about 270 mb of memory. Perhaps the system block has something to do with a fast incrising number of memory the application uses.

Steps to reproduce:
1. Starting Evince
2. Opening a *.pdf (about 7 mb)
3. Scaling to 300%


Actual results:
The Desktop is blocked and it takes some time to open the terminal or system monitor for killing it. Otherwise the application throws the below mentioned error-report.

Expected results:
The Document scaling to 300% without using such a great amount of memory (or what ever happens) and almost blocking my pc

Does this happen every time?
since first time scaling to 300% yes. Because when opening a document it always tries to zoom it in. 

Other information:
he 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 6287 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.)