Crash on Windows

[aza547]

Hello,

This is a bit of a weird one. I'm the developer of Warcraft Recorder (https://github.com/aza547/wow-recorder), an electron application which uses OBS via the "obs studio node" (https://github.com/stream-labs/obs-studio-node) project. At the heart of it, libobs is doing all the heavy lifting of recording and encoding.

I have a user reporting that libobs is crashing for them when using the application, I have crash logs which I've attached, apologies if they may be slightly different than the normal format as a result of the wrapping by the OSN project. It's a slightly outdated version of libobs (I'm limited by what OSN provide) and decent chance this is induced by a misconfiguration of libobs itself.

The bottom line is I don't understand the stack trace coming from libobs in the crash and would like to get some more understanding of what we're trying to do at the point of crashing. It looks to me that the top of the stack is here: https://github.com/obsproject/obs-s...e90c813f846425ab2/libobs/util/platform.c#L704, which sounds like a fairly innocent method.

[000:04:05:02.675.760.700][28220][Info] [ffmpeg muxer: 'recording'] Writing file 'D:\Gameplays\World Of Warcraft\.temp/2024-05-03 20-43-18.mp4'...
[000:04:09:34.376.141.500][18348][Info] ST: os_generate_formatted_filename obs64
[000:04:09:34.376.185.100][18348][Info] ST: os_generate_formatted_filename obs64
[000:04:09:34.376.210.700][18348][Info] ST: os_generate_formatted_filename obs64
[000:04:09:34.376.305.700][18348][Info] ST: os_generate_formatted_filename obs64
[000:04:09:34.376.335.300][18348][Info] ST: UnhandledExceptionFilter KERNELBASE
[000:04:09:34.376.357.700][18348][Info] ST: RtlCopyMemory ntdll
[000:04:09:34.376.382.900][18348][Info] ST: _C_specific_handler ntdll
[000:04:09:34.376.403.700][18348][Info] ST: _chkstk ntdll
[000:04:09:34.376.422.000][18348][Info] ST: RtlFindCharInUnicodeString ntdll
[000:04:09:34.376.441.200][18348][Info] ST: KiUserExceptionDispatcher ntdll
[000:04:09:34.376.467.100][18348][Info] ST: x264_10_threadpool_delete libx264-164
[000:04:09:34.376.488.700][18348][Info] ST: x264_8_threadpool_delete libx264-164
[000:04:09:34.376.512.900][18348][Info] ST: x264_8_frame_shift libx264-164
[000:04:09:34.376.536.600][18348][Info] ST: x264_8_frame_shift libx264-164
[000:04:09:34.376.559.600][18348][Info] ST: x264_8_frame_shift libx264-164
[000:04:09:34.376.582.900][18348][Info] ST: x264_8_frame_shift libx264-164
[000:04:09:34.376.606.500][18348][Info] ST: x264_8_frame_shift libx264-164
[000:04:09:34.376.633.100][18348][Info] ST: x264_encoder_invalidate_reference libx264-164
[000:04:09:34.376.652.000][18348][Info] ST: beginthreadex msvcrt
[000:04:09:34.376.670.400][18348][Info] ST: endthreadex msvcrt
[000:04:09:34.376.691.500][18348][Info] ST: BaseThreadInitThunk KERNEL32
[000:04:09:34.376.707.500][18348][Info] ST: RtlUserThreadStart ntdll
[000:04:09:34.376.709.900][18348][Info] ST: unknown function
[000:04:09:34.390.916.400][18348][Info] Server finished 'HandleCrash', crashpad will now make a sentry report

Many thanks for any insight.

Regards,
Alex

 

[koala]

This is a forum for OBS users, not a forum for OBS development or for development of applications derived from the OBS api. If you're a developer yourself, you need to start investigating and debugging that issue yourself, as any other developer. The stack trace information and source code how OBS generates a file name is hardly any information we as high level users of the original OBS will understand and can support.