http://bugs.kde.org/show_bug.cgi?id=177213
--- Comment #2 from Oscar Fuentes <ofv wanadoo es> 2008-12-08 21:18:50 --- The problem, as it seems, is not restricted to the djvu backend. A large pdf shows it too: Open a large pdf document, such as http://open-std.org/JTC1/SC22/WG21/docs/papers/2008/n2588.pdf Press the PageDown key and keep it pressed. Keep an eye on `top` or other memory reporting tool, looking at the Xorg process. On the Kubuntu machine, the memory skyrockets after reaching around page 500, but the X process already was using 700 MB of RES memory, so maybe some empty buffers were filled before requesting new memory. This high memory usage of X is something I'm investigating and it's the way I found the problem with Okular. I've observed that sometimes not all the memory used by X is freed after Okular closes, so this memory can be a remannt from previous Okular sessions. To make less plausible the hypothesis of a bug on the X server distributed with Kubuntu 8.10, tried another X server: xming 6.9.0.23 running on Windows 2000. Okular was ran on the Kubuntu machine as okular --display ahost:0 thedoc.pdf The memory consumption was evident: starting at 23MB when Okular is executed, it reaches 200 MB after scrolling 70 pages. xpdf, with the same document, does not change the memory used by the X server no matter how much pages are displayed. -- Configure bugmail: http://bugs.kde.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel