Application crash on close.
Posted: Wed Oct 11, 2017 1:36 pm
Hi,
My company has recently tried upgrading the SDK we use from 6.0.318 - 6.0.322.7 and we are now experiencing crashes when closing the application. This crash seems to only happen on certain documents (have been able to cause the crash with multiple documents) and even then, only on certain machines. Windows 10 machines seem to be able to handle the document, while Windows Server 2012 cannot (from what we tested). The only indication of what might be causing the error is from the problem signature on crash:
Problem signature:
Problem Event Name: BEX
Application Timestamp: 4ba2084b
Fault Module Name: PDFXEditCore.x86.dll
Fault Module Version: 6.0.322.7
Fault Module Timestamp: 598df614
Exception Offset: 000321a3
Exception Code: c0000409
Exception Data: 00000007
OS Version: 6.2.9200.2.0.0.272.79
Additional Information 1: 7865
Additional Information 2: 78659391c08b2d0e3a148a4fff50623d
Additional Information 3: 679b
Additional Information 4: 679bcca6f787ef88e9e6b34c4be2e2f2
We unfortunately could not narrow down the issue, so please let me know if anything is needed to do so.
Thank you,
Justin
My company has recently tried upgrading the SDK we use from 6.0.318 - 6.0.322.7 and we are now experiencing crashes when closing the application. This crash seems to only happen on certain documents (have been able to cause the crash with multiple documents) and even then, only on certain machines. Windows 10 machines seem to be able to handle the document, while Windows Server 2012 cannot (from what we tested). The only indication of what might be causing the error is from the problem signature on crash:
Problem signature:
Problem Event Name: BEX
Application Timestamp: 4ba2084b
Fault Module Name: PDFXEditCore.x86.dll
Fault Module Version: 6.0.322.7
Fault Module Timestamp: 598df614
Exception Offset: 000321a3
Exception Code: c0000409
Exception Data: 00000007
OS Version: 6.2.9200.2.0.0.272.79
Additional Information 1: 7865
Additional Information 2: 78659391c08b2d0e3a148a4fff50623d
Additional Information 3: 679b
Additional Information 4: 679bcca6f787ef88e9e6b34c4be2e2f2
We unfortunately could not narrow down the issue, so please let me know if anything is needed to do so.
Thank you,
Justin