How to Diagnose Word Memory Leaks

If Word grows in memory usage until it slows down your entire system or crashes, you might have a memory leak. A memory leak happens when Word does not release RAM after closing a document or completing a task. This article explains how to identify a memory leak in Word and what steps to take to confirm the problem.

Why Word Leaks Memory and How to Spot It

Word is a 32-bit application by default, meaning it can use up to 4 GB of virtual memory on a 64-bit version of Windows. A memory leak occurs when Word allocates memory for an object such as a document, image, or undo step but does not release it after the object is closed or deleted. Over time, the unreleased memory accumulates, causing Word to consume more RAM until it reaches its limit or exhausts available system memory.

Common causes include buggy add-ins, corrupted document elements like large embedded images or complex tables, and problems with the hardware graphics acceleration feature. Word’s own code can also leak memory in specific scenarios, such as when repeatedly using the undo stack in a very large document or when opening and closing many documents in a single session.

The first step in diagnosis is to confirm that Word is actually leaking memory rather than simply using a lot of memory for a large file. A leak is characterized by a steady increase in memory usage that does not decrease after closing documents or performing normal operations.

Steps to Diagnose Word Memory Leaks

Use Task Manager to monitor Word’s memory usage over time. Then run Word in Safe Mode to test for add-in interference. Finally, check the Event Viewer for crash logs that point to memory-related failures.

1. Open Task Manager and locate Word’s process
   Press Ctrl+Shift+Escape to open Task Manager. Click the Processes tab. Find Microsoft Word in the list. If you do not see it, open Word first and then switch back to Task Manager. Right-click the column headers and select Memory to ensure the memory column is visible. Note the current value under the Memory column, which shows the private working set in MB.
2. Record baseline memory usage
   With no documents open, write down the memory value. A baseline of 50 MB to 150 MB is normal. If the baseline is above 300 MB with no documents open, you may already have a leak.
3. Open and close a document while watching memory
   Open a document that is 10 to 50 pages long. Watch the memory value increase. Close the document without closing Word. Wait 10 seconds. The memory value should drop back to near the baseline. If it stays elevated by more than 50 MB, you have a memory leak.
4. Repeat the test with a different document
   Open a second document of a different type, such as one with embedded images or tables. Close it and observe whether memory returns to baseline. If memory climbs after each document without dropping, the leak is reproducible.
5. Run Word in Safe Mode
   Close Word. Press Windows Key + R, type winword /safe, and press Enter. Word opens in Safe Mode without add-ins. Repeat the open-and-close test from steps 2 through 4. If memory usage returns to baseline after each document in Safe Mode, the leak is caused by an add-in.
6. Check Event Viewer for memory-related crashes
   Press Windows Key + R, type eventvwr.msc, and press Enter. Expand Windows Logs and click Application. Look for Error events with Source “Microsoft Word” or “Application Error.” Double-click an event and note the Exception Code. Codes like 0xc0000005 (access violation) or 0xc0000017 (not enough quota) can indicate memory exhaustion caused by a leak.
7. Disable hardware graphics acceleration
   In Word, go to File > Options > Advanced. Under Display, check the box for Disable hardware graphics acceleration. Click OK and restart Word. Repeat the open-and-close test. If memory usage stabilizes, the GPU rendering path was causing the leak.

If Word Still Shows Abnormal Memory Usage

Memory does not drop after closing a document

If memory stays high after closing a document, the document itself may be corrupted or contain objects that Word cannot release. Try opening the document in Word Online or saving it as a new file using File > Save As. If the memory usage drops after saving as a new file, the original file had a structural problem.

Word crashes with an out-of-memory error

If you see a message that says “Word cannot complete the save due to a file permission error” or “There is not enough memory or disk space,” the leak may have exhausted available RAM. Force close Word via Task Manager (select Microsoft Word and click End task). Restart Windows before opening Word again. If the error returns quickly, run the Safe Mode test again to confirm add-in involvement.

Memory leak occurs only with a specific add-in

If the leak stops in Safe Mode, the culprit is an add-in. To identify which add-in, disable them one by one. Go to File > Options > Add-ins. At the bottom, set Manage to COM Add-ins and click Go. Uncheck all add-ins, restart Word normally, and re-enable add-ins one at a time while testing memory after each restart.

Word Memory Leak Diagnosis Methods Comparison

Method	What It Detects	Time to Complete
Task Manager monitoring	Real-time memory growth pattern	5 to 10 minutes
Safe Mode test	Add-in caused leaks	5 minutes
Event Viewer analysis	Crash events with memory-related exception codes	2 minutes
Hardware acceleration disable	GPU rendering path leaks	2 minutes plus restart

After completing these steps, you will know whether the memory leak is caused by an add-in, a specific document, the GPU rendering feature, or Word itself. If the leak persists in Safe Mode and with hardware acceleration disabled, the problem is a bug in Word. In that case, repair your Office installation by going to Settings > Apps > Microsoft 365 > Modify > Quick Repair. If the leak continues, file a report through the Word feedback system with the Task Manager data and Event Viewer logs attached.