Steady Increase in the memory consumed by PDFXChangeViewer

[saasira]

Hi,
I just installed PDFXchangeViewer and really liked the software very much.
However, I noticed that though it starts using a modest 20 MB , the more pages we view in PDFXChangeViewer the more memory it consumes.
When I scrolled across 100 pages in 500 page PDF Book, the memory consumed by PDFXChangeViewer increased to a whopping 250+ MB.

The same activity when done using Foxit PDF reader, it sill held less than 25 MB, perhaps 5-10 MB increase from the time it started up.
So, this looks like a bug in PDFXChangeViewer software. I'm reporting this bug to you because I like this software and want it to be improvised.

I hope you fix this bug soon,
waiting to try out a version that will have a fix to this bug.
until then,
bye,
Samba

[John - Tracker Supp]

Samba - its not a bug, PDF-XChange 'Cache's' the pages to allow you to scroll through the file without delays as you progress.

Memory is released after a short delay and you can also limit the amount of memory allowed using the option :

Edit menu -> Performance as required if this causes you specific problems.

In these days of high spec PC's (many with Gigabytes of RAM now and virtual memory etc) - we use whatever resources allowed within basic prescribed limits (I think 50% is auto setting) - but feel fre to define your own as detailed above.


HTH

[Lzcat - Tracker Supp]

Actually Auto setting for now is equal to 25% of the avail physical memory, so if your PC has 2GB RAM Viewer will use up to 512MB.

Of course you can adjust this setting as described above, but note that this is the total limit per application, not per document, so if you set it to too low a value and open several documents Viewer will need to reload and redraw pages even if you will navigate between two pages in the same document .

If a page renders slowly you will be forced to wait, wait, wait ... Do not worry if the Viewer use "too much memory" for some documents - it will free it after short timeout - e.g. if the Viewer is minimized for example(about 30 seconds now), or after a long if not (up to 10 minutes for inactive data); and of course it will free it almost immediately when the document is closed.


Optimal memory limit settings depend on the typical documents you generally need to work with. If they are simple and render fast (text, no large images and complex drawings) - you may set it to fairly low value and get good performance. But if your documnets are complex (for example a PDF created from CAD applications, diagrams like theese, etc) more memory for caching is required to achieve acceptable performance. So feel free to tune up the Viewer for your hardware and your needs.

Hope that helps

[Stokes]

I see this same answer several places online, but that's not the behavior I see in Windows 7.

I'm running Windows 7 64-bit on a machine with 8GB of RAM. When I visit a page in Firefox with a large PDF, the memory consumption grows beyond the limit I've set, and each tab grows independently, not the whole plugin as some have described.

So with only Firefox running, with about 10 tabs open, 3 of them PDFs, my task manager shows 3 PDFXCview.exe processes running. In the UI for each tab, they are all set at 10%.
But in Task manager, one of them is using 1,202,060K of "Memory (Private Working Set)". The second is using 1,206,608K, and the third is at 1,234,804K and climbing.

Occasionally, without any activity on my part, even if I'm idle and walk away, one of the processes will climb to over 7GB and my system will slow to a crawl. The version I installed was very recent, the .exe says it's version 2.5.188.0.

Stokes.

[Stefan - PDF-XChange]

Hello Stokes,

Please ensure that you are using build 193, as the memory leak in the plug in that you are describing was present in an older build and should have been fixed.

The installation file for the latest build can always be downloaded from here:
www.tracker-software.com/PDFXVwer.zip

Best,
Stefan

[Stokes]

Yeah, I realized after I posted that I should probably check for a newer release. I had only installed it a few weeks ago, but it looks like the issue's been fixed. There is another option related to memory now (fixed MB instead of percentage) and everything appears to be working.

Thanks for the reply,
Stokes.

[Paul - PDF-XChange]