Player crash after 4 hour and 13 minutes
KurtKomell opened this issue · comments
Hi,
Player crash because of out of memory excemption.
Logfile show this:
04:13:45.520 (Error): Updating Shader Resource View failed: HRESULT: [0x8007000E], Module: [General], ApiCode: [E_OUTOFMEMORY/Out of memory], Message: Für diesen Vorgang sind nicht genügend Speicherressourcen verfügbar.
04:13:45.546 (Error): Updating Shader Resource View failed: HRESULT: [0x8007000E], Module: [General], ApiCode: [E_OUTOFMEMORY/Out of memory], Message: Für diesen Vorgang sind nicht genügend Speicherressourcen verfügbar.
2023_07_31-23_31_44_692.log
What can i do?
Thank You for your Support.
Hi @KurtKomell . I'm sorry to hear that. Can you provide more details so I can narrow down the potential problem? Were you using video-playback by any chance?
I use the ndi Input and spout Input to in different PCs. I can send you the exportfolder for the Player.exe.
Oh. I can see that. The NDI-Plugin we're using seems to have some memory and resource-leaks.
Which resolution did you use for the transferred image?
Hi i use 1080p or 720p in both situation the player stop after 4 or 5 hours. It doesnt matter to be spout or ndi in. I think it is a problem of the Nvida rtx. I cannt Test it on a intel system. I do this later. Now i have a inquirey to show my installation from 7 am till 6 pm. So i would be nice to here from you with a solution. I can load my export folder up and send to you. Maybe i try to reboot the system all 4 hours, thats not the best way but a workaround. Thank you very much.
Hi Kurt. A link to the export-folder would be very useful. You can send me a private DM on discord or post it here.
After some experimentation, I could reproduce a similar problem wit the player: For me the timing was;
It's quite interesting that you had a out of memory exception just before the crash.
But it's quite strange that the suspent-times are sooo close together.
I will try to investigate further.
Some sites recommended to increase TdrDelay but I don't believe that this is related to the current issue.
https://learn.microsoft.com/en-us/windows-hardware/drivers/display/tdr-registry-keys
It looks like the freeze is occurring after 1024^2 frames which probably means there is a resource leak, e.g. in the handling of SRVs (the tier 2 limit for them being 1M). I will try to investigate further.
However the only real definition for this value was in:
https://learn.microsoft.com/en-us/windows/win32/direct3d12/hardware-support
Maximum number of descriptors in a Constant Buffer View (CBV), Shader Resource View (SRV), or Unordered Access View(UAV) heap used for rendering
This description doesn't sound related to a resource leak problem, though.,,
However in other featureset constant table this number does NOT show up...
- https://learn.microsoft.com/en-us/windows/win32/direct3d12/hardware-feature-levels
- https://learn.microsoft.com/en-us/windows/win32/direct3d11/overviews-direct3d-11-resources-limits
- https://microsoft.github.io/DirectX-Specs/d3d/archive/D3D11_3_FunctionalSpec.htm#26%20Constant%20Listing%20(Auto-generated)
It took some time to narrow this down but now it should be fixed in the next version.