PDF XChange Forum

Hello,

we have the following issue in Windows 10 Version 1703 and PDFSaver (Version 4 or 6). Windows 10 below Version 1703 is all fine!

If we batch convert many doc files to pdf (> 10000, dependend on filesize), at a certain point pagefile.sys begins to grow until operation system gives memory error messages.
At this point you have to reboot windows.

We reproduced it on different pcs also with your testapplication "CexApi" (modified to loop).

Is this a known issue?

Regards,
Peter

Hello Peter,

You are the first one to report this but it should still be investigated. The people that can look at this are in our Canadian office - so I've passed this topic along to them, and they will get back to you when they get to the office (it's still the middle of the night over there).

In the mean time if you can send us a copy of that modified "CexApi" test project - it will save some time to our devs when they start their investigation.

Regards,
Stefan

Hello Stefan, thanks a lot.

A modified sample is attached to this post.

You can use the following steps to reproduce:

- "Print .doc-File"
- File to print: (a larger file with more pages leeds to earlier crash)
- Klick "Go"

You can stop the loop by clicking the "cancel button" wich appears after "Go"

regards
Peter

Hi Peter,

Thanks for the sample project.
I've passed it along to a colleague who said that it is very useful to have it, but he is in our Canadian office and the investigation is taking a bit longer. We will post back here as soon as we have some further news!

Regards,
Stefan

Thanks.
One thing I forgot to mention.

It is not only related to word doc. You can also use a text file or any other file ...

Regards,
Peter

Hi Peter,

Thanks for the update.
My colleagues are still working on this. At the moment it seems like a leak in windows code, but for now we do not have a firm confirmation and are still looking.

Regards,
Stefan

Are there any news in this matter?

Regards,
Peter

Hello Peter,

I've just asked my colleagues for an update - and will let you know as soon as I know more!

Regards,
Stefan

Hello Peter,
Please check if you can reproduce the problem on Windows 10 with "2017-07 Cumulative Update for Windows 10 Version 1703 (KB4025342)" installed (see Settings->Windows Update->Update History).

Indeed, Windows 10 Version 1703 Build 15063.483 resolved it.
Thanks.