Fed up with Monosnap crashes?
Switch to Maxisnap.

The three crash modes

Monosnap's crashes on Windows break down into three mostly-distinct failure modes. Knowing which one you're hitting is useful context — though the fix for all three is the same.

GPU renderer crashes. These show as a sudden close of the application, often with an "application failed to initialize" dialog on the next launch. The root cause is Chromium's GPU process failing to communicate with the display driver. Users with recent NVIDIA RTX drivers or AMD Radeon drivers report this most frequently. Monosnap's Electron base means it inherits every Chromium GPU bug.

GDI handle exhaustion. Windows limits the number of GDI objects a single process can hold (the default cap is 10,000). Monosnap's multi-monitor capture pipeline doesn't always release handles after each capture. On a long enough session, the count creeps up until an allocation fails and the app terminates silently.

Out-of-memory crashes. As the memory leak grows, eventually the process crosses a limit — either the OS virtual address space limit for a 32-bit process or a user's system pressure limit. The app dies. Windows Event Viewer will show an "AppCrash" event with monosnap.exe and an exception code.

Why Maxisnap doesn’t hit these

Maxisnap is a 64-bit native application. It doesn't use a Chromium GPU process, so the first crash class is architecturally impossible. GDI handles are released in finally blocks after every capture, so handle exhaustion can't creep up. And the flat memory profile rules out OOM.

The v2.x series has been stable for months of continuous running in internal and user testing. If a crash does happen, the crash handler writes a log to %APPDATA%/Maxisnap/maxisnap.log that you can email to support — and since the app is actively maintained, the fix ships in the next release, not three years later.