vMix memory leak (RADAR_PRE_LEAK) and out-of-memory fixes

What it looks like in your log

Event Name: RADAR_PRE_LEAK_64
P1: vMix64.exe

Why does Windows say vMix has a memory leak, and how do I stop it?

RADAR_PRE_LEAK_64 is Windows Resource Exhaustion Detection saying that vMix64.exe kept allocating memory and not releasing it (a leak or a very large production), often logged as Windows Error Reporting event 1001 or "Windows successfully diagnosed a low virtual memory condition" (event 2004). It does not mean vMix crashed yet, but a process that keeps growing slows down, drops frames and eventually dies with an out-of-memory crash. Typical triggers are many large video, image or title inputs, browser and web-page inputs, third-party codecs or virtual cameras, and running a very long show without a restart.

How to fix it

1. Watch vMix64.exe in Task Manager (Details tab) during a show: steady growth over hours confirms a leak, a jump when you add an input points at that input.
2. Update vMix to the latest build and install the latest GPU driver.
3. Close inputs you are not using, replace huge videos and images with proxies or smaller files, and limit browser/web-page inputs.
4. Uninstall third-party codec packs and virtual cameras you do not need, then test again.
5. Make sure the PC has enough RAM (32 GB is a comfortable minimum for multi-input 1080p productions) and a large Windows page file.
6. For long events, restart vMix between sessions; if it keeps happening, send the Event Viewer entry and your vMix version to vMix support.