Unexpected Crash

[Darius1968]

The attached log file reflects an unexpected freeze-up & crash of IMatch.  While it was in the freeze-up, almost all of my 16 GB RAM was in use by IMatch, whereas IMatch usually uses around 1 GB RAM. 

[Mario]

Windows WIC / DirectX is running out of memory. The Viewer tries to counter this by releasing memory (removing pre-cached files from memory).
Still, Windows is running out of memory.

Sometimes this happens with corrupted files when Windows WIC has trouble to process the image data and gets into a frenzy allocating gigabytes of memory...

If you can reproduced this by viewing the same files in the Viewer, check the last files loaded. Usually re-saving the in an image editor 'fixes' them and Windows WIC has no longer problems loading them.
Tip: You can search for the word peak  which is logged by IMatch every time it reaches a new memory peak (memory consumption by IMatch).
Note: It is normal that the Viewer uses up to 80% of the available memory for caching. But not more.