https://bugs.kde.org/show_bug.cgi?id=388854
--- Comment #25 from Rooty <zy...@gmx.us> --- (In reply to Oliver Sander from comment #24) > I don't think that this would help. The argument would then be that the > "use little memory"-option has its price, which is slower loading times. > > What is needed is more precise information on what all that memory is > actually used for, where it gets allocated, etc. You could try to figure > that out using memory profiling, code auditing, experimenting etc. Only > then one can really tell whether we are talking about a bug, a design flaw, > or a feature. the idea it needs more RAM to load pages faster is a very tempting leap, but fairly moot. chromium and evince load pages blazingly quickly at very little memory cost (compared to Okular at low, not normal or aggressive) while at the same time rendering those very same pages (granted, evince does a stunning job of messing up the font rendering). okular scrolls faster but it doesn't render the pages as quickly (regardless of its RAM usage), and when set up at low, after a while just refuses to render them at all. we can try profiling its memory usage but the fact remains that regardless of where the RAM goes it still doesn't pass muster (which is very unlike most KDE software nowadays...) -- You are receiving this mail because: You are watching all bug changes.
