MMV crashes when streaming from PLEX and trying to export movie at the same time?

[Lynx_TWO]

I noticed that MMV crashes after a few minutes when streaming from my PLEX server and trying to export a movie at the same time; so basically, if another video is encoding on the GPU, MMV doesn't seem to handle that well. Is there a way to tell MMV to use fewer resources on the GPU, or another workaround? If not, that's fine, and I'll just make sure I'm not using PLEX at the same time as MMV, but figured it would be worth asking

[Terry Payman]

This is not an authoritative answer, but supports your suggested workaround.

I recall that in real-time (non-exporting) operation MMV crashes in a "GPU memory full" situation.

I think that is because memory allocation is determined
dynamically by the NVIDIA driver and Magic can only see GPU memory availability in retrospect. It cannot know how much will be needed for an imminent MMV operation.

The situation is further complicated if other apps (eg PLEX) are also using GPU. MMV uses an external encoder when exporting,. I don't know, but this too might be using GPU.

A few thoughts if you wanted to investigate, rather than merely avoid.

If you use MMV in real time on the Plex server you can monitor available GPU memory in the Magic window
you would be able to see how much the available memory decreases when PLEX streaming is running too.

Exporting might well use extra GPU memory, especially if at a higher resolution.

I can't remember if this memory reading is available when MMV is exporting, but you could always run a second instance of MMV to monitor GPU memory at the same time if not.

[Lynx_TWO]

Thanks for the feedback! Upon further investigation, MMV was still crashing even without running PLEX, so I went to the Windows event viewer and found this after I uninstalled and reinstalled MMV, and it still crashed:

"Faulting application name: Magic.exe, version: 0.0.0.0, time stamp: 0x6501e052 Faulting module name: ntdll.dll, version: 10.0.26100.4768, time stamp: 0x95c61958 Exception code: 0xc0000374 Fault offset: 0x000000000011dc45 Faulting process id: 0xEAD4 Faulting application start time: 0x1DC14F5590D9946 Faulting application path: C:\Program Files\Magic\Magic.exe Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll Report Id: 2dec4c8c-e083-4921-b29d-499fd219248d Faulting package full name: Faulting package-relative application ID:"

Given this, I went ahead and ran it in compatibility mode for Windows 8. So far, it's rendering at 4k without crashing, but I will report back with the logs if it crashes again