The mouse cursor gets choppy, starts missing input etc. Once it took me ten minutes to be able to close down Evince. Now this part is of course not a problem with evince - but is this really the way it's supposed to be? Other OS:es never do this - mouse cursor always responds regardless of how much thrashing is going on. Could it be something like the X-server being swapped out? CPU usage never peaks during this period.
This PDF with a scanned schematic eats up all my memory when I open it: www.crownaudio. com/pdf/ legacy/ MT-1000schemati c.PDF
http://
The mouse cursor gets choppy, starts missing input etc. Once it took me ten minutes to be able to close down Evince. Now this part is of course not a problem with evince - but is this really the way it's supposed to be? Other OS:es never do this - mouse cursor always responds regardless of how much thrashing is going on. Could it be something like the X-server being swapped out? CPU usage never peaks during this period.