Skip to main content
Participant
October 6, 2026
Question

Is anyone starting to get agmcalls.log and agmmemorystats.log files created in directories that PDFs are exported/stored in?

  • October 6, 2026
  • 1 reply
  • 132 views

Since updating Acrobat to 26.002.21996 (installed October 6, 2026), two plain-text files named agmcalls.log and agmmemorystats.log are being created in folders that contain PDFs. If you delete them, they come back the next time the user opens or previews PDFs in that folder.

Environment:
- Windows 11 25H2
- Adobe Acrobat 26.002.21996 (AGM.dll file version 8.0.5.1)
- Acrobat Reader 26.002.21901 is also installed on the same machine; it was not updated
- The PDF preview handler is Adobe's pdfprevhndlr.dll
- The folder is on a mapped network drive; I have not yet confirmed whether local folders are affected too

What the files contain:
- agmcalls.log starts with "AGM Call Counts" and lists call tallies grouped by component (RasterPort, ColorSpace, PaintServer, Function, Image, etc.), followed by CTTAG: lines (CoolType counters)
- agmmemorystats.log starts with "*** AGM shutting down ***" and contains a memory allocation table per object type (AVGlobals, PMGlobals, RasterPort, PathPoints, etc.)
- No file paths, document text, or user data, only counters

This looks like Adobe Graphics Manager (AGM.dll) diagnostic output that is written to the process's current working directory when the rendering engine unloads. Both files share the same timestamp, which matches when the user opened or previewed PDFs in that folder. No environment variables or registry settings on the machine reference AGM or debug logging.

Questions:
1. Is this a known issue with 26.002.21996 (debug or statistics logging left enabled)?
2. Is there a registry setting, environment variable, or preference that turns this output on or off?
3. Is a fixed build available or planned?

 

    1 reply

    Participant
    October 6, 2026

    I was about to post this same question. I have several users having this exact same issue. My environment is 25 user Windows 2019 Terminal server running version 26.002.21996.0