Bug 155774 - "agressive memory allocation" does not work
Summary: "agressive memory allocation" does not work
Status: RESOLVED DUPLICATE of bug 147977
Alias: None
Product: kpdf
Classification: Applications
Component: general (show other bugs)
Version: 0.5.8
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: Albert Astals Cid
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-01-14 19:19 UTC by Oliver Grimm
Modified: 2008-01-16 09:56 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Oliver Grimm 2008-01-14 19:19:28 UTC 
Version:           0.5.8 (using KDE KDE 3.5.8)
Installed from:    Debian testing/unstable Packages
OS:                Linux

To reproduce do
- start KPDF
- select options|memory_usage --> agressive
- open a PDF file with some artwork such that it takes some time to render the pages
- hit your favorite short key for "next page"
--> it takes a few seconds until the page is rendered

Expected behaviour is that the new page shows instantly as it is "preloaded in memory"; at least that is what the hint text for "agressive memory allocation" promises. Going back and forth shows pages instantly which makes me believe that page caching does work in general here.
Comment 1 Pino Toscano 2008-01-14 19:29:22 UTC 
Are you using continuous mode or not?
Comment 2 Oliver Grimm 2008-01-16 09:27:44 UTC 
I am using the single page mode.
Comment 3 Pino Toscano 2008-01-16 09:56:57 UTC 

*** This bug has been marked as a duplicate of 147977 ***