OBS Crashing...

D

DocRedstoneYT

New Member
I cannot find exactly why, and the analyzer doesn't have any information other than it is critical, which I kinda gathered already after OBS crashed while closing. Attached is the most recent crash log, I am not sure what exactly is causing, I did recent perform an update of obs, although, it recently crashed before that update and I was hoping the update would of solved my problem, but didn't. Thank you in advance to anyone who finds out more information than I have! I have attached all the recent crash logs in hopes to help find out exactly what is going on.
 

Attachments

  • Crash 2023-12-13 23-18-44.txt
    107.5 KB · Views: 34
  • Crash 2023-12-10 20-48-43.txt
    70.3 KB · Views: 10
  • Crash 2023-12-10 11-52-39.txt
    105.7 KB · Views: 10
  • Crash 2023-12-09 23-43-25.txt
    75.3 KB · Views: 9
  • Crash 2023-12-06 00-27-34.txt
    74.8 KB · Views: 11
  • Crash 2023-12-05 23-52-14.txt
    150 KB · Views: 9
Suslik V

Suslik V

Active Member
There are two different crashes in the logs.

First, from v30.0.0 of OBS:
Code: 
000000496682F818 00007FF8F4785070 4030AAAA9F7B5AEA 000001AFAC0A5DC0 0000509A012BD018 0000000000000000 lua51.dll!0x7ff8f4785070
000000496682F820 00007FF8F5432B62 0000509A012BD018 0000000000000001 0000000000000000 0000000000000000 obs-scripting.dll!lua_tick+0xa2
is crash in the scripting related to rendering. If this still happens in OBSv30.0.2, then possible workaround - find the ".lua" script that may cause this and remove it from the scripts list of OBS (main menu Tools > Scripts).

Second crash, is common for v30.0.0 and v30.0.2 of OBS:
Code: 
000000BDE10FB890 00007FFB89D30B7D 000000BDE10FBFA0 00007FFB89D51CF0 000000BDE10FBA79 000000BDE10FB910 qt6widgets.dll!0x7ffb89d30b7d
000000BDE10FB8E0 00007FFB863F5633 000000BDE10FB978 00000240C942F0A0 0000024000000000 00007FFB890BD29C obs-websocket.dll!`Utils::Platform::SendTrayNotification'::`2'::<lambda_1>::<lambda_invoker_cdecl>+0x33
is UI crashed when it accessed from obs-websocket during alert display. Possible workaround - either try to disable alerts from websocket server of OBS (main menu Tools > WebSocket Server Settings > Enable System Tray Alerts) or try to disable whole websocket functionality (main menu Tools > WebSocket Server Settings > Enable WebSocket server)

Crash in websocket is surely OBS internal bug because it also reproducible in virtual environment (I have no exact steps or pattern so far, but it seems that it even ignores disabled tray icon state, and happens only on OBS exit).
 
Last edited:
Suslik V

Suslik V

Active Member
Faulty shutdown sequence looks like this (example):
Code: 
14:00:34.290: ==== Recording Start ===============================================
14:00:34.290: [ffmpeg muxer: 'simple_file_output'] Writing file 'C:/Temp/2023-12-14 14-00-33.mkv'...
14:00:46.562: ==== Shutting down ==================================================
14:00:47.230: All scene data cleared
14:00:47.230: ------------------------------------------------
14:00:47.326: [ffmpeg muxer: 'simple_file_output'] Output of file 'C:/Temp/2023-12-14 14-00-33.mkv' stopped
14:00:47.326: Output 'simple_file_output': stopping
14:00:47.326: Output 'simple_file_output': Total frames output: 367
14:00:47.326: Output 'simple_file_output': Total drawn frames: 139 (392 attempted)
14:00:47.326: Output 'simple_file_output': Number of lagged frames due to rendering lag/stalls: 253 (64.5%)
14:00:47.396: [obs-websocket] [WebSocketServer::onClose] WebSocket client `[::1]:49764` has disconnected with code `1006` and reason: End of File
14:00:47.424: Tried to call obs_frontend_get_system_tray with no callbacks!
14:00:53.229: QWaitCondition: Destroyed while threads are still waiting
14:00:53.229: QWaitCondition: Destroyed while threads are still waiting
14:00:53.232: [obs-websocket] [WebSocketServer::Stop] Server stopped successfully
14:00:53.232: Tried to call obs_frontend_remove_event_callback with no callbacks!
Normal shutdown sequence looks like this (example):
Code: 
14:27:27.454: ==== Recording Start ===============================================
14:27:27.454: [ffmpeg muxer: 'simple_file_output'] Writing file 'C:/Temp/2023-12-14 14-27-27.mkv'...
14:27:42.961: ==== Shutting down ==================================================
14:27:43.063: [obs-websocket] [WebSocketServer::onClose] WebSocket client `[::1]:49869` has disconnected with code `1001` and reason: 
14:27:43.067: All scene data cleared
14:27:43.068: ------------------------------------------------
14:27:43.159: [ffmpeg muxer: 'simple_file_output'] Output of file 'C:/Temp/2023-12-14 14-27-27.mkv' stopped
14:27:43.159: Output 'simple_file_output': stopping
14:27:43.159: Output 'simple_file_output': Total frames output: 452
14:27:43.159: Output 'simple_file_output': Total drawn frames: 471
14:27:43.284: [obs-websocket] [obs_module_unload] Shutting down...
14:27:43.285: [obs-websocket] [WebSocketServer::ServerRunner] IO thread exited.
14:27:43.286: [obs-websocket] [WebSocketServer::Stop] Server stopped successfully
14:27:43.287: Tried to call obs_frontend_remove_event_callback with no callbacks!
14:27:43.287: [obs-websocket] [obs_module_unload] Finished shutting down.
14:27:43.365: [Scripting] Total detached callbacks: 0
14:27:43.366: Freeing OBS context data
14:27:43.399: == Profiler Results =============================
...and here goes profiler data
 
Suslik V

Suslik V

Active Member
You must log in or register to reply here.
Top