Participant

Answered

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

70 replies
15432 views
Translate

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?

Anand Sri BhattacharyaCorrect answer

Community Manager

Hello @josecale

I hope you are doing well. The team has identified the root cause and has identified the fix. The fix will be available soon. We will update you once the fix is available.

Thanks for your cooperation on this.

Regards,

Anand Sri.

Show previous replies

D

defaultfg0s5oumjrhp

Participant

experiencing the same issue with this as well. Do we have a update?

Translate

Anand Sri Bhattacharya

Community Manager

Hello @defaultfg0s5oumjrhp

I hope you are doing well, and sorry for the trouble. The product team is working on isolating the issue and working on a fix. There is no ETA for the patch yet, but we will update the thread as soon as the fix is available with the public release.

Also, try the suggestion highlighted by the Adobe Employee and let us know if this fixes the issue for you:

Regards,

Anand Sri

Translate

D

Dazzling_perspectivedc86

Participant

@Anand Sri Bhattacharya any update on when the patch will be released? Thank you

Translate

M

Melodic_Beeccbf

Participant

Based on putting the logs in copilot and the amount of files we are getting generated by staff it looks like someone left a debug flag on when the patch was released.

Do you have an ETA on when a patch will be pushed out to fix this?

Translate

Anand Sri Bhattacharya

Community Manager

Hello @Melodic_Beeccbf

I hope you are doing well, and sorry for the trouble. The product team is working on isolating the issue and working on a fix. There is no ETA for the patch yet, but we will update the thread as soon as the fix is available with the public release.

Also, try the suggestion highlighted by the Adobe Employee and let us know if this fixes the issue for you:

Thanks,

Anand Sri

Translate

T

TROY01AB

Participant

We are using 32 bit due to plugin restrictions.

Translate

Meenakshi Negi

Community Manager

Hi All,

Please check and confirm if the issue occurs when the protect mode is set to Off. Share the screenshots of the settings. You can check the following:

Go to Menu > Preferences > Security (Enhanced).
On the right check under Sanbox Protections.
If it is off, turn on and check if the issue still occurs.

Let us know how it goes.

Thanks,

Meenakshi

Translate

E

excited_curiosityaa84

Participating Frequently

Hi Meenakshi
Not the issue here. no Sandbox enabled. Tried to disable “enhanced security” (Aktiver udvidet sikkerhed), also not the issue. See attachment (in Danish).

Kr
Kim

Translate

E

excited_curiosityaa84

Participating Frequently

Hi

I have a customer that has the same probelms in a RDS server enviroment. Files are getting created when opening PDF file in Adobe Reader. Tried to delete file, then open PDF again, then files get created again. @Meenakshi Negi
It looks as debugging logs of some kind, so some one in dev. probertly released a version w/o disabling the debugging before compiling the new build :)
I’ve renamed files from *.log to *.txt so that i could attach them. Maybe this could help Troubleshoot.

I’ll warn my collegues, since we’re hosting a lot of customers that use Adobe Reader.

Translate

Participant

Same issue here. We need a fix for that. It fills all file share which the user is opening a pdf file then after he closes it. then the debug files is produced. Please release fix or disable the debugging feature

Translate

Meenakshi Negi

Community Manager

Hi All,

The team is investigating this issue and a bug ticket has been created for the same.

Could you please confirm if anyone is experiencing this behaviour with the Acrobat 64-bit version?

Thanks,

Meenakshi

Translate

D

Dazzling_perspectivedc86

Participant

Experiencing same issue. Any update?

Translate

W

wonderful_goalbeca

Participant

Facing the same issue. User was on Adobe Acrobat 26.002.21996 32-bit when the issue started happening. Updating them to Reader 2026.002.21931 didn’t resolve the issue.

Translate

D

DFWTechGuy

Participating Frequently

The timing makes this look very much like a regression in the 26.002.21996 build. The fact that both agmcalls.log and agmmemorystats.log appear after opening or previewing PDFs, and that they return after being deleted, is especially interesting.

The contents also sound like internal Adobe Graphics Manager statistics rather than normal Acrobat logging. I’d check whether the same behavior occurs with a local folder as well as the mapped network drive. If it does, that would make the network location less likely to be involved.

I’d also test the same PDFs with the previous Acrobat build, if you have a machine where 26.002.21996 has not been installed. Since Adobe’s current release information does not appear to document these AGM files as an intentional feature, reproducing the issue only on 26.002.21996 would be useful evidence for Adobe.

I would avoid manually deleting or changing registry/environment settings unless Adobe confirms a supported way to disable the statistics output. If this is debug logging accidentally enabled in the AGM component, it would be better for Adobe to provide a fixed build rather than disabling it through an undocumented setting.

If you can confirm whether the files are also created in a local folder and whether downgrading to the previous Acrobat build stops them, that would be a really useful comparison for this report.

Translate

Show more replies

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.