Version: 3.5.10 (using KDE 3.5.10) Compiler: gcc-4.3.2 OS: Linux Installed from: Gentoo Packages When viewing large files in kpdf it leads xorg to use all accessible memory. After viewing of 100 pages memory usage goes into 500 Megs and more.
Created attachment 33925 [details] valgrind log from kpdf session
KPDF caches the rendered pages internally, using the low-loevel graphics system (X11, in your case). Of course, it retains a policy about it, that you can set in the preferences, "Performance" section. 100 Mb of memory for 50 pages and more it is not that much. How much memory (RAM + swap) do you have in total?
After some investigation, it seems that even kpdf and okular when viewing pdf files, lead xorg into extremaly high memory usage. The strange is that this memory is listed by pmap command, but isn't listed when called xrestop at all. There are examples: Before opening of okular (just few lines from pmap): 5102: /usr/bin/X -br -novtswitch -quiet -nolisten tcp :0 vt7 -auth /var/run/xauth/A:0-Vs1HqS Address Kbytes RSS Anon Locked Mode Mapping 0000000000400000 1708 - - - r-x-- Xorg 00000000007ab000 8 - - - r---- Xorg 00000000007ad000 36 - - - rw--- Xorg 00000000007b6000 164 - - - rw--- [ anon ] 0000000001378000 75008 - - - rw--- [ anon ] 0000000040a9a000 8 - - - rwx-- zero And after viewing about 200 pages in okular (500 pages long document, 26 MB), the same as above: 5102: /usr/bin/X -br -novtswitch -quiet -nolisten tcp :0 vt7 -auth /var/run/xauth/A:0-Vs1HqS Address Kbytes RSS Anon Locked Mode Mapping 0000000000400000 1708 - - - r-x-- Xorg 00000000007ab000 8 - - - r---- Xorg 00000000007ad000 36 - - - rw--- Xorg 00000000007b6000 164 - - - rw--- [ anon ] 0000000001378000 634112 - - - rw--- [ anon ] 0000000040a9a000 8 - - - rwx-- zero As you can see, there is used over 600 MB of memory. The problem is that this situation lead regularry to extensive usage of SWAP, and the system stay unusable until xorg will be restarted.
Please mark it as duplicate of bug No 177213
It seams, that since installation of QT-4.5.2 it is much much better. Memory usage is growing until a defined level, and then stops.
*** This bug has been marked as a duplicate of bug 177213 ***