Forum rules DO NOT post your license/serial key, or your activation code - these forums, and all posts within, are public and we will be forced to immediately deactivate your license.
When experiencing some errors, use the IAUX_Inst::FormatHRESULT method to see their description and include it in your post along with the error code.
I am seeing a Process has stopped working error when I close my application randomly may be 30-40% of the time. Following are the details of the error that I get:
I am using VB6 and i am setting the variables that I use to Nothing in the Form_Unload method. I am calling the "pInst.Finalize" method in the unload function as well.
I've checked with a colleague from the dev team, and he says that unfortunately only with the description we can not help much.
We would need a sample project as well. Can you please prepare that one for us?
The application that is causing this behavior is very large and complex and unfortunately I cannot create a stripped down version of it to provide to you. Are there any best practices that I can go through and see if anything is missing in my code that might be causing this issue?
Well I'm almost 100% sure that some object is being left alive when you call Finalize. Check in that direction - I'm afraid that we can't tell anything else.
I have been working on this and have a pattern and code to reproduce this issue.
I am using the VB6 and the latest version of Core Api 6.0.322.7 (per web page) or 7.0.323.2 (per the actual file that is installed). However i can reproduce this issue with older versions of Core Api.
Just let the attached exe run for approximately 15 mins and close the application to produce the issue.
Please let me know if you are able to reproduce the issue.
Thanks for the sample project.
I will pass it along to Alex, but he said that because of some tasks he has today - he will be able to investigate this only tomorrow.
We will post here as soon as there are any news!
Well what we can say is that some thread is still alive after shutdown and this causes this exception. We are not sure whether the problem is in VB engine or somewhere in our code that conflicts with the VB. We will try to investigate further.
Have you been able to find a fix for this? This is affecting our clients in Production and they are pressing hard for a fix. Can you give me an estimate that I can update my clients with?
Can you see if there is at least a work-around for this problem?
Our clients run this unattended in Production, and it can lock up their system for hours when it happens.
It's not something we have been able to trap, so unless a person is actively shutting the app down and is also
there to handle the error, then we have a lock up problem...
Hi Wayne,
Here it is. Please replace the original SDK DLLs with ones from the attached ZIP.
Actually for your VB6 application you need only 32-bit SDK DLL (PDFXCoreAPI.x86.dll).
Please let us know the outcome.
We've done a bunch of internal testing and the problem seems to be resolved.
We have yet to install it into a client environment for further testing, but it looks good so far!