I just had a crash report during a livestream but I don't know how to analyze.
Can someone help me?
Can someone help me?
How can I analyze a crash report?
- Thread starter Jurya
- Start date
Want To Learn
Member
If it's what I think you're asking...Go to the help menu - log files and upload current log file, so a popup will come up with choices to either copy that log or analyze it. If you click on analyze it that takes you to the obs site to analyze it. Or, you can copy it to attach it to your post here to ask questions. Good luck!
OBS Analyzer tool doesn't handle Crash Reports, that's the problem.
Want To Learn
Member
I'm not a programmer, but I would think if you posted your log file someone can help you to see what the issues are. However, I would suggest if you could open OBS to get into it then go into the settings under the file menu and look for scenes, make a backup then delete the scene, so that you can have a fresh start. Also, make a backup of your scripts to. After all this bring back everything a little at a time. I guess the easiest might be to start a brand new scene from the Scene Collections menu. It's like starting fresh. I do all this on a Mac, but it should be similar for a PC. Good luck!!.....Oh! forgot safe mode. Try it just to get in, but many things are disabled. Hope this helps!
Oops! i just checked on my virtul PC and it is a bit different than what I had said. I don't use it much, so I really don't know. You should watch youtube videos to learn how to back up OBS first.
Last edited:
Crash reports are more for the developers, and people who really like that level of involvement and intimate understanding. They're effectively a snapshot of where the program actually was at the time of the crash, with no opportunity to make any kind of readable summary itself. It just stops, right there, and dumps that out. Done.
If you've ever used a debugger, paused it, and looked at the actual contents of memory and where it is in the code at that moment, that's pretty much what a crash report is. It's up to you to figure out how it got to that point.
I don't look forward to rebuilding my Linux rigs every two years, but I intentionally do it that way instead of upgrading in place, just for the clean-out. Stuff just builds up over time, as your usage changes and you forget to delete stuff that you don't use anymore, etc.
If you've ever used a debugger, paused it, and looked at the actual contents of memory and where it is in the code at that moment, that's pretty much what a crash report is. It's up to you to figure out how it got to that point.
Yes to all of that. Yes, it's a hassle, but you do need to clean things out from time to time.
I don't look forward to rebuilding my Linux rigs every two years, but I intentionally do it that way instead of upgrading in place, just for the clean-out. Stuff just builds up over time, as your usage changes and you forget to delete stuff that you don't use anymore, etc.
Suslik V
Active Member
Code:
Thread 21E4: (Crashed)
Stack EIP Arg0 Arg1 Arg2 Arg3 Address
000000D1B8DFF248 000000025F309000 000002765463E2E0 000000D1B8DFF220 0000696326487DFB 0000696326487DCB <unknown>!0x25f309000
000000D1B8DFF250 00007FFEBD5BF922 00000276000028C0 000002765361CAA0 000000007FFE03B0 00007FFEC9C8081D mmdevapi.dll!Ordinal12+0x1232
000000D1B8DFF280 00007FFEBD5BF8C6 0000000000000000 0000000000000000 000000D1BD30FB90 00007FFE81DBC506 mmdevapi.dll!Ordinal12+0x11d6
000000D1B8DFF2B0 00007FFEBD5BF874 0000027638AE8170 00000276444CC801 00000276444CC8E8 000002765361CAA0 mmdevapi.dll!Ordinal12+0x1184
000000D1B8DFF2E0 00007FFEBD5A89DB 0000027638AE8170 00007FFEBD580000 000000D1B8DFF648 00000276444CC801 mmdevapi.dll!Ordinal21+0x1d1b
000000D1B8DFF310 00007FFEBD5A5A1F 0000000000000000 000000D1B8DFF648 000000D1B8DFF648 0000000900000000 mmdevapi.dll!Ordinal31+0x481f
000000D1B8DFF390 00007FFECC850A4E 0000000000000000 0000000000000001 0000000000000000 00000276546C9B30 ntdll.dll!0x7ffecc850a4e
000000D1B8DFF4B0 00007FFECC852201 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ntdll.dll!0x7ffecc852201
000000D1B8DFF810 00007FFECAA6E8D7 0000000000000000 0000000000000000 000004F0FFFFFB30 000004D0FFFFFB30 kernel32.dll!0x7ffecaa6e8d7
000000D1B8DFF840 00007FFECC8DFBCC 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ntdll.dll!0x7ffecc8dfbccWant To Learn
Member
When you uninstall it you're just uninstalling the OBS application and should not affect your files, so if you simply install the OBS app everything automatically comes back? I know it's a good idea to back it all up, but is it necessary in this case? Thanks in advance!
Doesn't hurt. It's *supposed* to be okay, but re-configuring software installations in general, has a nasty habit of messing with stuff anyway.
Better though, would be to fully document in some other format - whatever works for you - how to rebuild the rig from scratch. Then if even the backup doesn't work and it's all hosed, you can nuke it from orbit and start over. And you can tweak things from that documentation and set it up in a way that actually does work, instead of having to insist on the specific pattern of bits in the backup that for whatever reason might refuse to.
Suslik V
Active Member
@Want To Learn
uninstall of the plugin should be done in the way the author of the plugin recommends. If no instructions given then you simply reversing installation steps (usually by removing files added during installation process).
The re-installation of OBS itself requires separate thread for discussion and not related to this issue. In general, some installers designed to remove whole content in the destination folder before writing new files (the whole folder will be removed and recreated again), others - just overwrites existing files in the destination folder and does not touch anything else already existing in this and child folders.
uninstall of the plugin should be done in the way the author of the plugin recommends. If no instructions given then you simply reversing installation steps (usually by removing files added during installation process).
The re-installation of OBS itself requires separate thread for discussion and not related to this issue. In general, some installers designed to remove whole content in the destination folder before writing new files (the whole folder will be removed and recreated again), others - just overwrites existing files in the destination folder and does not touch anything else already existing in this and child folders.
Want To Learn
Member
Thank You Suslik V. It explains why one or two plugins that I just copied into the plugins folder worked and some did not.