Skip to main content
B
bm10
Participant
November 8, 2019
Question

Adobe Reader - large process handle count/memory leak

  • November 8, 2019
  • 2 replies
  • 3710 views

We're running Adobe Reader 19.012.20040 in a Citrix environment and experiencing issues with the servers running out of physical memory, bringing the server to a crawl. These servers have 96GB of RAM each and normal usage is around 20GB. Hoping that someone has experienced this something similar. When people start reporting getting out of memory errors and slowness, we open Task Manager and review the process with highest handle count.

 

Everytime this occurs, it's a single AcroRd32.exe process with over 45,0000 handles open. Task manager also shows over 90GB of RAM in use, but none of the processess show high memory usage, only the high handle count of AcroRd32.exe. As soon as that Adobe Reader process is killed, memory usage drops from >90GB  to <20GB within several seconds.

 

We checked the PDF the user was working on and made sure protected mode is disabled in preferences. It's happening with different users, PDF files, and different Citrix servers. Anyone have reccomendations?

This topic has been closed for replies.

2 replies

K
komod
Participant
August 5, 2020

Could you solve the problem? We have the same issue and we can reproduce it with files created in abbyy finereader with watermarks. But neither abbyy oder adobe can help us with this problem.

    B
    bm10Author
    Participant
    August 5, 2020

    No, we have never figured out the root cause of this issue and still experiencing this. It's interesting you mention Abby as this program is also in use in the environment. Was there certain steps you go through to re-produce the problem? I can try and replicate in our environment as well.

    K
    komod
    Participant
    August 6, 2020

    It looks like the problem in our environment is just with these documents, created in abbyy finereader with a watermark.

    When one of these documents is open with adobe reader we experiencing the same issues which you mentioned the temrinalservers running out of physical memory. 

     

    T
    Test Screen Name
    Legend
    November 8, 2019

    Reader is a 32-bit app, so no Acrord32.exe process can use more than 2 GB of RAM. Since this isn't usual, it may be worth examining which handles it is using to see what most of them are.

    B
    bm10Author
    Participant
    November 8, 2019

    Right, and task manager never shows it using high memory. The only thing that shows abnormal is the handle count on the process (usually >40 times higher than any other process). Is there a particular method to determine what handles Adobe Reader has? Thank you.

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices