Skip to main content
Participating Frequently
August 16, 2021
Question

Acrobate.exe not getting close (Killed)

  • August 16, 2021
  • 1 reply
  • 676 views

Acrobat.exe not getting closed/ killed even after quitting the application.

Please find the code snippet below.

Public Sub Close()
Try
AcroPDFObj.gPDDOC.Close()
AcroPDFObj.gAVDOC.Close(False)
If Not AcroPDFObj.gApp Is Nothing Then
AcroPDFObj.gApp.Exit()
End If Catch ex As Exception
End Try
AcroPDFObj.gAVDOC = Nothing
AcroPDFObj.gPDDOC = Nothing
AcroPDFObj.gApp = Nothing
AcroPDFObj = Nothing

GC.Collect()
GC.WaitForPendingFinalizers()
End Sub

Please suggest what else needs to write to get Acrobat Process killed from task manager.

This topic has been closed for replies.

1 reply

BarlaeDC
Community Expert
Community Expert
August 20, 2021

Hi ,

 

I don't think there is anything else you can do from an Acrobat point of view, although I have noticed in the past that the Exit(); command is more of a can you exit if you are not doing anything else please. It may be that you can use something else to actually kill Acrobat, but if you user actually has Acrobat open for a reason then this would probably not go down well with them.

Participating Frequently
August 26, 2021

Hi,

I'm ready with killing Acrobat.exe, but i have multiple application running which are using acrobat.exe, so directly killing process won't help.

As acrobat works on  single thread, it have only one process for acrobat running at a given instance on time.

Is there any way to have diffrent processid for each acrobat instance

 

Thanks

BarlaeDC
Community Expert
Community Expert
August 26, 2021

Hi,

 

These used to work for Acrobat too, although they are not supported and may not work as expected, and I don't have a windows machine so I can't test them, but here you go:

https://stackoverflow.com/questions/619158/adobe-reader-command-line-reference