OBS crash and MKV file deleted

[thekiradrummer]

So I was recording 2 separate obs applications for facecam & gameplay. After just under 1 hour of recording I had an OBS crash which stopped my gameplay recording but not the facecam. After reopening & restarting the gameplay recording I checked to see if the MKV file was in the folder and found it was not. Ive checked my entire PC & external hard drive for the recording and it is nowhere to be seen. On top of this the start of the facecam footage is also corrupted so another MKV file unfortunately that is unusable. Does anybody have any advice or info as to why this happened?

This is the log from the gameplay footage.

 

[Suslik V]

Can you post the crash report as well? Look in main menu Help > Crash Reports.

 

[thekiradrummer]

Of course yeah! Thank you :)

 

[Suslik V]

Unhandled exception: 80000003
...

Thread 6278: libobs: graphics thread (Crashed)
Stack            EIP              Arg0             Arg1             Arg2             Arg3             Address
000000010142F828 00007FFC1CFF1732 000000010142F8A0 00007FFC9E6B11C0 0000000000000000 0000000000000000 obs.dll!os_breakpoint+0x2
000000010142F830 00007FFC1CFA7230 0000000000000002 0000018744805B00 000000010142F8B9 000001870049414E obs.dll!bmalloc+0x30
000000010142F860 00007FFC302A1F66 000001874D38E170 000000010142FC80 000001874472B1E8 00007FFC1CF9F048 win-capture.dll!cursor_capture_icon+0xf6
000000010142F920 00007FFC302A2225 0000000000000000 000000000000000D 0000000000000000 000001874D38E160 win-capture.dll!cursor_capture+0x65
000000010142F970 00007FFC302A98A3 000000000000000C 000001874534BCC0 000001874534BCC0 000001875A77F880 win-capture.dll!game_capture_tick+0x893
000000010142FAE0 00007FFC1CF82AF2 000001874534BCC0 000000000000000D 000001875A77CC40 000000000000000E obs.dll!obs_source_video_tick+0x572
000000010142FB50 00007FFC1CF94F3F 00000187441B6100 000000092300285B 0000000000000008 0000000000000000 obs.dll!tick_sources+0x29f
000000010142FBB0 00007FFC1CF988C8 0000000000000000 00000391AC0FB7D4 000001874C60B040 0000000000FE502A obs.dll!obs_graphics_thread_loop+0x1c8
000000010142FC60 00007FFC1CF98FBF FFFFFFFFFFFFFFFF 000000001AFC77F8 000000010142FD70 000001874C610130 obs.dll!obs_graphics_thread+0x12f
000000010142FD10 00007FFC1CE81461 00000187448176A0 0000000000000000 0000000000000000 0000000000000000 w32-pthreads.dll!ptw32_threadStart+0x171
000000010142FD80 00007FFC9D9837B0 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ucrtbase.dll!0x7ffc9d9837b0
000000010142FDB0 00007FFC9F8DE8D7 0000000000000000 0000000000000000 000004F0FFFFFB30 000004D0FFFFFB30 kernel32.dll!0x7ffc9f8de8d7
000000010142FDE0 00007FFCA07714FC 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ntdll.dll!0x7ffca07714fc

Edit: This means: not enough resources to complete the task. Out of free RAM. OS manages memory available for the application. You may try to give to OBS a bit higher priority in Advanced settings. Or maybe it's just a new bug in the "vulkan" enabled game capture.
See below.

 

[thekiradrummer]

I'll have to check the RAM thing but hopefully it doesn't happen again. I'm testing the next recording to go to my PC instead of external hard drive so hopefully I find out soon what works

 

[prgmitchell]

Of course yeah! Thank you :)

Hi thanks for reporting this, it doesn't relate to your RAM but a fix has been submitted today for it based on your crash report.

win-capture: Fix crash if cursor size is zero by RytoEX · Pull Request #12182 · obsproject/obs-studio

Description Fix crash if cursor size is zero. Instead, in a condition where the cursor size is zero, don't attempt to allocate and draw a cursor. Motivation and Context Don't want to c...

github.com

Should hopefully make it into the next release of OBS.