v10.5.0.393 - problems in IPXC_Document.WriteToFile if using custom IProgessMon SOLVED

[zarkogajic]

Hi Support,

Eh ... this one was hard to locate.

It seems 393 version has some newly introduced bug inside IPXC_Document.WriteToFile when using IProgressMon parameter.

Here's what I know so far:

I have my implementation of IProgressMon using with WriteToFile(...)

My app crashes, various weird exceptions are reported including : "out of memory", "AV in module 'ucrtbase.dll'".

The call to IPXC_Document.WriteToFile happens in a separate thread.

Even if my implementation of IProgressMon does nothing - still crash.

I've also noted that the same custom implementation of IProgressMon, used in, for example, IPXC_Document.PlaceHeadersAndFooters() works as expected (also not in main thread).

If null is used for IProgressMon in WriteToFile - no crash (but then no usable progress indication ofc)

Yes, same code works with v9.X with no issues.


-žarko

[Vasyl - PDF-XChange]

I checked the code around the WriteToFile and cannot see any potential reason for such problem. Can you provide a simple example to reproduce it on our side?

[Vasyl - PDF-XChange]

Perhaps we found the reason for the trouble and fixed it. The fix will be in the upcoming build.

[zarkogajic]

Hi Vasyl,

Thanks.

p s.
Still need sample?

-ž

[Stefan - PDF-XChange]

Hello zarkogajic,

I believe that a sample is not needed for now. Please check next week when the new build is out whether the fix Vasyl mentined above helps, and if a sample is still needed after that we will request it!

Kind regards,
Stefan

[zarkogajic]

Hi Stefan,

Agreed, thanks.

-žarko

[Stefan - PDF-XChange]