Skip to main content
TD47OZ
TD47OZ
Inspiring
July 3, 2022
Answered

4GB Memory leak in Adobe Reader DC

  • July 3, 2022
  • 2 replies
  • 4644 views

ADOBE READER Version 2022.001.20142 (64-BIT), Windows 10 21H2 (OS Builld 19044.1806).

I have had a few hangs and blank (black) screens recently, and thought it was an OS or Video Driver issue, but tonight, I had an "Out of memory" message, as well has programs not starting, so I  started the Task manager, and spotted a 92% memory usage of over 4GB for Adobe Reader DC.

I closed the 4 files I had open in Adobe Reader, and things were better, BUT I still saw a very high memory useage. I used the Task manage to create a dump file of the process, and as I expected that was over 4GB as well!!

Is there a way I can share this large file with Adobe Tech Support please?

    This topic has been closed for replies.
    Correct answer TD47OZ

    Hi @TD47OZ @Cyril5FC6 

    Following up to check if your issue is resolved or if you are still experiencing this problem. 

     

    ~Tariq


    Hello Tariq, thatns for checking the status of my situation. Since I have been putting in all the recent available updates to the Adobe Reader, things have been stable, so I am hopefull that the original memory leak bug, when I have had several itms open in the reader, for a few hours, seems to have gone away. You can mark this as closed, and I will open a new case when I get any new issue. Thanks for your support and concern.

    2 replies

    Amal.
    Community Manager
    Amal.Community Manager
    Community Manager
    April 4, 2024

    Hi there

     

    Could you follow the steps as described below to collect the required logs and share them via any cloud storage of your choice for further investigation of the issue.

     

    1. Follow the step 1 of UMDH_Documentation.pdf
       

      Note: do the setup before launching the Acrobat.

    2. After that Launch the Acrobat and follow the step 2 of UMDH_Documentation.pdf
       

      and rename the created file snap.txt to snap_before.txt.

    3. Perform the workflow due to which memory leak is happening.

    4. Now again follow the step 2 of UMDH_Documentation.pdf
       

      and rename the created file snap.txt to snap_after.txt.

    5. Share snap_before.txt & snap_after.txt.

    6. Now follow the step 3 of UMDH_Documentation.pdf
       

       for cleanup to use Acrobat again.

     

     

    ~Amal

    Amal.
    Community Manager
    Amal.Community Manager
    Community Manager
    July 4, 2022

    Hi there

     

    Hope you are doing well and sorry to hear that.

     

    As you have the recent version of the application, please try to repair the installation from the help menu (Win Only) and reboot the computer once and check.

     

    You may also try to reset the Acrobat preferences as described here https://community.adobe.com/t5/acrobat-discussions/how-to-reset-acrobat-preference-settings-to-default/td-p/4792082

     

    Please go to Edit > Preferences > Page Display > Under rendering, Uncheck 'Use Page Cache' > Click OK and reboot the application and see if that works for you

     

    Let us know how it goes.

     

    Regards

    Amal.

    TD47OZ
    TD47OZAuthor
    Inspiring
    July 5, 2022

    Hello, thanks for your reply. As you say, I DO have the latest version (installed very recently), so I would HOPE that your product should not suddenly need a "repair" finction done to it after such little usage (unless of course internal caches are being badly managed due to lack of defensive code, and bounds checking functions). I menion internal caches, becuase it is interesting that you mention turning Page Cacheing off. I have seen this mentioned on other (older) posts about memory leaks, and possibly similar post about related Adobe products (OCR processing/conversions), and certainly larger "pro" products like After Effects, Lightroom, and Photoshop.

    Obviously there is no such thing as "perfect software", and because developers in all companies tend to use "Common Function Libraries" to use/reuse common Object Code routines, then common bugs dues to lack of defensive code for unexpected conditions can occur in ANY released software product that contains these.

     

    I am happpy though, to follow your recommendations, and as I had ALREADY seen that commonly mentioned fix about turning off "Page Cache", it does make me wonder if these types of issues has been around for some time, as "High memory Usage" crops up a lot for several Adobe products. I HAVE now got it unticked. BUT, I will continue to monitor the Adobe Reader product more closely for Memory Leaks from now on, and report accordingly.

    As I have taken the trouble of creating a dump file (now compressed to about 675MB), I would have thought that Adobe developers here MIGHT be interested in analyzing it, to see IF there are any clues in it to know where to check (i.e. what sub-routines migh want a code review), to provide more stability for Adobe Product users.

     

    If Adobe IS interested in fixing thier deficient code (as it WAS that product creating the issue, and NOT lack of resources in my system or operating system), please idicate a way I can share this dump with them. Thanks.

    Amal.
    Community Manager
    Amal.Community Manager
    Community Manager
    July 6, 2022

    Hi there

     

    Thanks for sharing the observation. You may upload the dump file to any cloud storage and share the link with us so that we can get it checked by our engineering team.

     

    Regards

    Amal

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