Acrobat 26.002.21931 (64-bit) creates 10,000+ USER objects / 12,000+ windows, exhausts the Windows desktop heap and freezes the whole PC

Question

Product: Adobe Acrobat (64-bit) 26.002.21931, Continuous track, Creative Cloud subscription

OS: Windows 11 Home 25H2, build 26200.9550

Hardware: Dell XPS 17 9710, Intel i7-11800H, 64 GB RAM, NVIDIA RTX 3050 Laptop

SUMMARY

Since mid-September 2026 my laptop froze completely 8 times (screen locked, no input, Sign out hangs, only the power button works). Windows never blue-screened. Each freeze is preceded by the System event log entry Win32k 704 "A desktop heap allocation failed", followed by Explorer.EXE, ctfmon.exe and dwm.exe crashing.

A per-process monitor running every minute shows Acrobat.exe is the process filling the desktop heap:

- 2026-09-23 14:17 -> 14:18: Acrobat.exe went from 205 to 10,000 USER objects (the per-process cap) within one minute, right after a second Acrobat window opened a PDF. Session total went 3,577 -> 13,241. The PC froze about 30 seconds later.

- 2026-09-23 14:42: a freshly launched Acrobat.exe, sitting on the Home screen with NO document open, owned 12,105 top-level and child windows (counted with EnumWindows/EnumChildWindows). Every other process on the machine combined owned about 650.

- Even idle, Acrobat.exe holds about 1,390 windows for hours.

STEPS TO REPRODUCE (on my machine)

1. Launch Acrobat, stay on the Home screen. Count windows owned by Acrobat.exe (Process Explorer or EnumWindows): ~1,400 immediately, sometimes >12,000.

2. Open a PDF in a second Acrobat window. USER objects for Acrobat.exe jump to the 10,000 cap within a minute.

3. Once the interactive desktop heap (default 20 MB) is exhausted, Windows logs event 704 and the shell crashes; the PC must be power-cycled.

EXPECTED: Acrobat holds a few hundred windows/USER objects like any other desktop app.

OBSERVED: Thousands of windows at idle, 10,000 USER objects after opening a PDF, desktop heap exhausted, whole PC frozen.

WORKAROUNDS

- Uninstalling Acrobat 26.002.21931 (2026-09-23). No freeze since.

- Raising the interactive desktop heap to 40 MB only delays the freeze.

SETTINGS AT THE TIME

- Generative AI features were enabled during the freezes; the 12,105-window burst happened with them still enabled.

- Acrobat was the default PDF handler.

I can provide the per-minute CSV log of USER/GDI/window counts per process for 2026-09-22/23, Windows System and Application event log extracts around each freeze, and a snapshot of all processes at the moment of the 704 event. Has anyone else seen Explorer crashes or full-PC freezes with this build?

DFWTechGuy · Answer

That sounds more like an Acrobat resource leak than a normal Windows desktop heap issue, especially since Acrobat is reaching 10,000 USER objects and thousands of windows while idle.

The fact that uninstalling 26.002.21931 stopped the freezes is a pretty strong clue. I would keep the heap at its default rather than increasing it further, since that only delays the failure.

I'd report this to Adobe with the exact build, Win32k Event 704, USER/window counts, and the reproduction steps. If possible, also test the same workload with Generative AI disabled and note whether the window count still grows.

The per-minute CSV and event logs you mentioned would be very useful for Adobe to reproduce this.

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.