Acrobat Pro DC crashes after my plugin open a document the second time

New Here ,
Apr 01, 2021 Apr 01, 2021

Copy link to clipboard

Copied

Here is my piece of code:

{
        ASFileSys fileSys = ASGetDefaultUnicodeFileSys();
        ASPathName pathName = ASFileSysCreatePathName(fileSys, ASAtomFromString("WinUnicodePath"), doc.filePath, NULL);
...
 
This code is called from an external program using menu item execution:
Set app = CreateObject(AcroExch.App)
app.menuItemExecute("ADBE:MyCommand")
 
My scenario is following:
  1. Launch the command: it opens the document in Acrobat
  2. Close Acrobat manually: Acrobat disappear but a process remains in the background
  3. Launch the command again: it opends the document and then crashes Acrobat outside of the plugin code

 

Additional information: the document contains some annotations. If annotations are not present, it seems to work.

 

Thank you in advance for your help

TOPICS
Acrobat SDK and JavaScript, Windows

Views

77

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Correct Answer

New Here , Apr 01, 2021 Apr 01, 2021
Thank you for your quick answer.Looking at the handles, I've found that is came from the handles locked by the client. Once released, it works fine.

Likes

Translate

Translate
Adobe Community Professional ,
Apr 01, 2021 Apr 01, 2021

Copy link to clipboard

Copied

Hi,

 

Have you registered for the WillClose ( I think that is the name) notification and make sure that you are releasing all handles to the document or windows the document may use?

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Apr 01, 2021 Apr 01, 2021

Copy link to clipboard

Copied

Thank you for your quick answer.

Looking at the handles, I've found that is came from the handles locked by the client. Once released, it works fine.

 

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Apr 02, 2021 Apr 02, 2021

Copy link to clipboard

Copied

LATEST
 

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines