[Okular-devel] [Bug 177213] High X server memory consumption

Albert Astals Cid tsdgeos at terra.es
Mon May 25 01:22:38 CEST 2009


--- Comment #13 from Albert Astals Cid <tsdgeos terra es>  2009-05-25 01:22:37 ---
Okular is not the most memory hungry document viewer out there, at least it's
at the same level of kpdf ;-)

It's fast for local viewing because to paint anything on X, it must be a X
pixmap, if you already have a X pixmap you just have to paint it, if you have
something else, you have to create one and then paint it. And creating X
pixmaps is not a negligible time.

And it's not about page rendering (that is creating the image that represents
the page) speed it's about drawing speed (that is putting that image in front
of the user), it's different, page rendering speed is going to be the same as
that's all done in the CPU it's drawing speed of a rendered page that is much

And probably you got a NO because you weren't attacking the problem from the
correct point, if you suggest removing page caching or not using X pixmaps by
default obviously you get a no, if you suggest having a hidden setting that
disallows the use of non local memory, that would different. But now that i
think i'm not sure it makes sense, because once you've disallowed any X pixmap
caching even if you don't explicitely use X pixmaps for rendering you are going
to use them implicetely because it's the only thing that can be rendered, so
you won't gain anything at the end, it'll have the same remote memory usage at
the end.

Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

More information about the Okular-devel mailing list