Bug 102528 - kpdf: not preloading next page
Summary: kpdf: not preloading next page
Status: RESOLVED INTENTIONAL
Alias: None
Product: kpdf
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Albert Astals Cid
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-03-26 13:08 UTC by missive
Modified: 2011-10-15 15:30 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description missive 2005-03-26 13:08:53 UTC
Version:           3.4.0 (using KDE 3.4.0, Gentoo)
Compiler:          gcc version 3.3.5 (Gentoo Linux 3.3.5-r1, ssp-3.3.2-3, pie-8.7.7.1)
OS:                Linux (i686) release 2.6.11-gentoo-r4

I have the kpdf Performance->Memory Usage set to "Aggressive" but still when switching to the next page, there is a delay as the page is rendered.

Don't get me wrong here... kpdf in kde3.4 is like lightning. It just seems like the setting is not doing what it says it will do.
Comment 1 Enrico Ros 2005-08-22 13:47:11 UTC
KPDF tries to balance the used memory against the free one. Aggressive tries to eat all your memory but preventing the tedious swapness. If it doesn't preload the next page it means that really free memory is very low.. better wait than turn on the HD drive.
Let me know if it preloads next page when the system has plenty of really free memory.
Comment 2 Iñaki Baz Castillo 2005-12-09 16:17:31 UTC
I have Memory Usage set to "Agresive", but it doesn't preload next page. This is the out fo "free" command in console:

  #free
               total       used       free     shared    buffers     cached
  Mem:        774916     571284     203632          0      13896     186652
  -/+ buffers/cache:     370736     404180
  Swap:       514040        100     513940

Is it not enough to preload next page?
Comment 3 Darwin Te 2006-01-27 14:00:51 UTC
I have 1 gigabyte of RAM and few running applications.. same observation.. not preloading the pages keeps me waiting.
Comment 4 Luke 2006-03-06 08:33:54 UTC
I'm seeing the same problem with ~200MB free memory. In addition, pages previously rendered are immediately forgotten once out of view in "aggressive" mode.
Comment 5 Arne Schmitz 2006-06-23 14:55:14 UTC
I also experience this: The next page is not preloaded! Having 2GByte of RAM here (some hundred free). Please implement another strategy: "Always preload next page" which ALWAYS preloads the next (and maybe previous) page, but has variable strategy for other pages.
Comment 6 Arne Schmitz 2006-06-23 14:56:23 UTC
*** This bug has been confirmed by popular vote. ***
Comment 7 Malte 2006-12-17 17:25:16 UTC
I have set the memory usage to "normal". Every time I go to the next page I get the described rendering delay. But going pages backward (to the one I had already viewed) I can go up to about eleven pages back wihout a rendering delay. So KPDF has obviously enoug RAM for about 12 pages. I would really like to see it that KPDF renders the next page in advanced and caches a page less of the previous visited ones.
My KDE Version is 3.5.2
Comment 8 Pino Toscano 2007-01-05 00:32:59 UTC
We did some work for KDE 3.5.6 that should improve the situation a bit.
Feedback is appreciated and welcome, of course.
Comment 9 Malte 2007-08-29 23:51:21 UTC
With KDE 3.5.5 the behavior is now quite well for me. While setting the memory usage to "normal" he is loading the next page in advanced, setting it to "low", kpdf does not. Thats the behavior I had hoped for :-)
Comment 10 Pino Toscano 2007-12-31 12:27:16 UTC
Are you using non-continuous mode? Or continuous mode?
Comment 11 Arne Schmitz 2007-12-31 19:44:18 UTC
I am using non-continuous mode.
Comment 12 Pino Toscano 2008-02-06 12:27:00 UTC
Anyone: if you are *NOT* using continuous mode: bug #147977 is for you.
Comment 13 Frank Steinmetzger 2008-02-26 13:52:12 UTC
It already worked, I remember it must have been 3.5.5. Back then, a 600 page document used to eat up all of my 1GB of RAM (no swap). Now I have 3GB and KDE 3.5.7/3.5.8 (gentoo), but the mem is not used in the slightest, even though I have set it to aggressive. I even tried it on a fresh and clean user account - in case I had some broken setting from long ago. But KPDF doesn't obey the setting, no matter what it's set to.
Comment 14 missive 2011-10-15 15:30:36 UTC
I think this should just be closed wontfix. Okular works great and I think kpdf is defunct.