How do I analyze this crash report?

Yantor

New Member
How do you know? Is there anything I could do to fix it without removing the plugin?
Moreover, is there any other plugin I could use for the same result?
 

PaiSand

Active Member
I opened the crash report and looked at it, that's how I know.
You can't fix a pluing but you can ask the creator/maintainer to fix it, if the development of this plugin is still going.
You need to look for yourself in the plugins section or use the OBS built in (still in beta) audio capture.
 

Yantor

New Member
Jesus, what a dick!
Reason why I asked how do you know is because I'm trying to learn what to look for so I don't depend on people like you to tell me.

You don't know me, you don't know what I already did or didn't do before I came asking, so don't assume I didn't look for another plugin myself. If I came here to ask is because I have already exausted my options, preciselly because I don't like to deal with AH like yourself.

If your not going to provide decent support to what you say, keep your fingers away from the keyboard and let someone else do it you punk.
 

koala

Active Member
You open crash logs with some ascii text editor such as notepad that comes with Windows. Or after upload here in the forum, click on the link to show the file content.
At the top, there is some general information about the crash and some version info. Below are info sections, one for each thread. The top thread, just below the header, is the thread that crashed. Ignore all the numbers and look at the dll file listing on the rightmost column. Look from top to bottom through the list of dll's in that section and check if there is a dll listed that resides in the plugin directory of OBS and if that is a dll you installed for a 3rd party plugin. In your case, it's win-capture-audio.dll, and this is a 3rd party plugin.

If you don't have browser sources, there is a dll list with full path info at the end of the crash log, so you don't need to actually search for a dll file on your system. However, if you do use browser sources, the crash log is truncated and the dll list at the end is omitted.
 
Top