Help me analyze Crash Reports

[InfantryInk]

Hi everyone

First I just want to say I been on here for years ad this place has always helped me. This is my first time posting so I will try to be as clear as possible with my issues. My OBS has been randomly crashing a lot more lately and I've finally hit my breaking point. First I thought it was outdated or incompatible plugins which may still be the case but I can't tell anymore. I feel like its different everytime.

As of right now I just got windows 11 and OBS is crashing a lot more. Can someone help me analyze this crash report and tell me exactly what this instance was?


There is gonna be more crashes when I switch my scene collection and I will post them when it happens. Thank you to all those that help.

 

[prgmitchell]

Yes it would be a plugin, you'd need to remove them until you figure out which.

 

[InfantryInk]

Yes it would be a plugin, you'd need to remove them until you figure out which.

Isnt there a way to tell which one is causing issues? Or is it better to do it one at a time?

Only hard part is idk how to trigger the issue to test it. Its very random

 

[Suslik V]

Can you attach regular log file from this session?

 

[koala]

If you look into a crash log with a text editor, for example Windows notepad, you see a list of app threads present at the time of the crash. The top thread is the one that crashed, and at the right side you see a list of dll files that executed that thread. Usually, this is the place where you would see a plugin dll if a plugin crashed. However, in your log there's no plugin dll visible, so it's more difficult to troubleshoot. It may be a plugin corrupted some internal data structure so it crashed later somewhere else.

In your case, it seems OBS crashed while deleting a source. Do you have plugins that create their own source types? Or otherwise deal with addition/removal of sources? Add custom menus, custom UI? These would be the ones first to check, update or remove.

In the bottom of the crash log you see a list of all dlls involved in OBS, including all plugin dlls. I see you have the streamelements plugin installed. In the past that was a common source of all kinds of crashes, so I recommend you uninstall that first and see how OBS behaves.

 

[Suslik V]

OK. Details.

However, in your log there's no plugin dll visible...

It was already unloaded on application close. Application was about to close when dll function called (the thread next to the crashed program thread, see below, has info about closing OBS). But OBS running many threads, so it was not easy to close all properly...

Main error. This number has special meaning. In case of the "c0000005" it means that there was attempt to access the RAM that is already marked as "free" or occupied by other structures/processes/users etc:

Unhandled exception: c0000005
...

Next lines should be read from bottom to top. The top one is the latest command that is failed. Here it named "<unknown>" and it was at address "0x7ffc86c1f2b0" (some function call, nothing at this address anymore, so it is name "unknown"):

Thread 29A4: tiny_tubular_task_thread (Crashed)
Stack            EIP              Arg0             Arg1             Arg2             Arg3             Address
000000B6989FF798 00007FFC86C1F2B0 0000000000000000 000001E3B97077C0 00007FFC9D81BE98 000001E3AC243D60 <unknown>!0x7ffc86c1f2b0
000000B6989FF7A0 00007FFC9D7E20B2 000001E3AC246880 00007FFC9D81BE98 000000B6989FF840 0000000000000000 obs.dll!signal_handler_signal+0x122
000000B6989FF820 00007FFC9D79B69C 0000000000000000 000001E3B97077C0 0000000000000800 000001E3B97077C0 obs.dll!obs_source_dosignal+0x17c
000000B6989FF930 00007FFC9D7A0D79 000001E3B97077C0 000001E3B97077C0 000001E3B4AEFE20 00007FFC9D7A0D30 obs.dll!obs_source_destroy_defer+0x49
000000B6989FF980 00007FFC9D7DDFE4 0000000000000000 FFFFFFFFFFFFFFFF 000000B6989FFA40 000001E3B970EE60 obs.dll!tiny_tubular_task_thread+0x434
000000B6989FF9E0 00007FFD06331461 000001E3B96F58B0 0000000000000000 0000000000000000 0000000000000000 w32-pthreads.dll!ptw32_threadStart+0x171
000000B6989FFA50 00007FFD2F9237B0 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ucrtbase.dll!0x7ffd2f9237b0
000000B6989FFA80 00007FFD30BDE8D7 0000000000000000 0000000000000000 000004F0FFFFFB30 000004D0FFFFFB30 kernel32.dll!0x7ffd30bde8d7
000000B6989FFAB0 00007FFD3209C5DC 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ntdll.dll!0x7ffd3209c5dc

Thread 90C:
Stack            EIP              Arg0             Arg1             Arg2             Arg3             Address
000000B697F9F718 00007FFD32161FF4 0000000000000001 0000000000000000 000097FF8FCC1555 0000000000000246 ntdll.dll!0x7ffd32161ff4
000000B697F9F720 00007FFD2F41D1DF 000001E3B9703FA0 000001E3B9703FA0 0000000000000000 00000000000005F8 kernelbase.dll!0x7ffd2f41d1df

Shutdown sequence of OBS application:

000000B697F9F7C0 00007FFC9D7BC987 000001E3B9704008 0000000000000288 000001E3B9704008 0000000000000288 obs.dll!obs_free_data+0x367
000000B697F9F820 00007FFC9D7BDE03 0000000000000000 000000B697F9FB00 000000B697F9FDA0 000001E3AA359880 obs.dll!obs_shutdown+0x383
000000B697F9F870 00007FF644104BB2 00007FF64438430D 000001E300000000 0000000000000002 00007FF64438430D obs64.exe!OBSApp::~OBSApp+0x62

Just how OBS started:

000000B697F9F8A0 00007FF64410A334 000000B697F9FCE0 0000000000000001 0000000000000001 000001E3B5A5C370 obs64.exe!run_program+0xfe4
000000B697F9FCA0 00007FF64410B90A 0000000000000000 0000000000000000 0000000000000000 0000000000000001 obs64.exe!main+0x79a
000000B697F9FE80 00007FF64417EC6D 0000000000000002 0000000000000000 000001E3B5A6BA20 000001E3B5A4FD00 obs64.exe!qtEntryPoint+0x15d
000000B697F9FF10 00007FF64417E1E2 0000000000000000 0000000000000000 0000000000000000 0000000000000000 obs64.exe!__scrt_common_main_seh+0x106
000000B697F9FF50 00007FFD30BDE8D7 0000000000000000 0000000000000000 000004F0FFFFFB30 000004D0FFFFFB30 kernel32.dll!0x7ffd30bde8d7
000000B697F9FF80 00007FFD3209C5DC 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ntdll.dll!0x7ffd3209c5dc
...

You may not look at the rest of the lines, but the:

Loaded modules:
Base Address                      Module
...
00007FFC93AB0000-00007FFC93AC4000 C:\ProgramData\obs-studio\plugins\StreamDeckPlugin\bin\64bit\StreamDeckPlugin.dll
...

From previous reports I know that this plugin uses few other linked libraries, thus thing becomes complicated... Because this plugin lies out of OBS plugins dir - it usually comes out of scope when user looks for faulty plugins.

The "StreamDeckPlugin.dll" plugin a lot relayed on signals, so I would start form it.

 

[InfantryInk]

Most Recent Crash today

Log File from crash and right after but no crash file was created

 

[prgmitchell]

Most Recent Crash today

Log File from crash and right after but no crash file was created

Hi, as I mentioned what you're describing sounds like an issue with a plugin but additional logs won't give a more specific answer. Same response I gave a couple of weeks ago, it will take some trial and error on your end to figure out which.

 

[gmoney0505]

I have the same crash report with the same unknown and tiny_tubular_task_thread that is causing the crash. Copy this %PROGRAMDATA%\obs-studio\plugins into a file explorer address bar and delete that Stream deck folder and if you hadn't already done it uninstall the obs plugin in stream deck and you should be good after that.