By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.

Bug 2315

Summary: kpdf "forgets" a page as soon as no longer displayed, has to re-render to display it again
Product: TDE Reporter: Dan Youngquist <dan>
Component: tdegraphicsAssignee: Timothy Pearson <kb9vqf>
Status: RESOLVED WORKSFORME    
Severity: normal CC: bugwatch, kb9vqf, michele.calgaro, slavek.banko
Priority: P5    
Version: R14.0.1 [Trinity]   
Hardware: All   
OS: Debian Wheezy   
Compiler Version: TDE Version String:
Application Version: Application Name:
Bug Depends on:    
Bug Blocks: 2575    

Description Dan Youngquist 2015-01-17 19:34:43 CST
kpdf "forgets" a page as soon as it's no longer displayed, and has to re-render it to display it again.  It's as though Memory Usage is set to Low instead of Normal or Aggressive, but the setting makes no difference.

This works correctly in 3.5.13.2.  Unfortunately I didn't pay enough attention to be sure, but it was about the time I switched to R14 that I first noticed the problem.
Comment 1 Michele Calgaro 2016-02-07 06:22:00 CST
Dan,
I am having difficulties in replicating this bug.
Can you provide a sample document that shows the problem, plus your kpdf settings (screenshots would do) and explain how you can reproduce it? Thanks
Comment 2 Michele Calgaro 2016-08-12 06:59:59 CDT
Any news? I still can not replicate the problem.

I am considering closing the bug as "works for me" and eventually let people reopen it if they can provide a way to replicate the problem consistenly so that we can work on the problem.

Slavek, what's your opinion?
Comment 3 Michele Calgaro 2016-08-20 07:13:51 CDT
After discussion with Slavek, we have decided to close the bug since we have tried to replicate it unsuccessfully for too many times.

If anyone can observe the same behavior described by Dan and can replicate it systematically, please do not hesitate to reopen the bug.