Question / Help 64bit BrowserSource won't load & OBS crashes when shutting down

GrathiusXR

New Member
Been having heaps of problems with OBS 64bit over the past couple of months. Problems ranging from random crashes when changing scenes to it crashing when clicking the X trying to shut down OBS 64bit to now just tonight, no CLR source will load on 64bit but when running 32bit they load and work fine.

This includes BitBoss, Streamlabs Alert Box, Stream ajr, Twitch Chat and event list.

I have uploaded the latest log and wanted to get some help with regards to why this is happening. OBS used to work fine however, one random day when I switched scenes it crashed and I needed to restart my entire PC for it to not be a process anymore to load it up and use it again.

I've re-installed OBS and restarted my PC to no avail to have these load or work on 64bit. Am I Missing something?
 

Attachments

  • 2017-05-23 23-52-08.txt
    12.3 KB · Views: 12

GrathiusXR

New Member
Here is the last crash log of OBS when I used it last which was on the 4/5/2017. I have multiple crash logs ranging from the previous day to weeks back so not sure which will be best to determine the problem.
 

Attachments

  • Crash 2017-05-04 19-51-58.txt
    50 KB · Views: 7

R1CH

Forum Admin
Developer
The CLR Browser is only for OBS Classic. Not entirely sure what you're doing, but plugins are not compatible between OBS Classic and OBS Studio. If you want to use the browser source in a 64 bit OBS Studio, use the full installer from the homepage and it will be included.
 

GrathiusXR

New Member
My apologies let me re-word what I've written and explained in my original post.

Browser sources do not work in OBS 64bit anymore. They load and work flawlessly with 32bit.

When starting 32bit OBS everything loads, it works fine and even prompted me to update to the latest version. After updating I still have the problem. So I uninstalled OBS restarted my PC and then installed v18 again. I loaded up the 64bit version of OBS 64bit and still nothing, not even a prompt for a new update.

Loaded up the 32bit version and everything loaded up perfectly and it even prompted me to update to the latest version. Do either of my logs showcase anything that might be fundamentally wrong with my 64bit of OBS that I physically cannot understand or fix with a simple uninstall and re-install?
 

R1CH

Forum Admin
Developer
It would seem something is blocking your 64 bit OBS from accessing the internet. Check it's whitelisted in any antivirus / firewall software, and remove any 3rd party "network optimizer" or similar programs. A malware check may also be worthwhile as some winsock hijacks can cause this kind of behavior.
 

GrathiusXR

New Member
Windows Firewall has obs64 accepted. Windows Defender is the only anti-virus on my PC and has been for almost over a year now. obs64 used to work perfectly fine up until a few months ago where it randomly crashed when changing a scene. It hasn't been the same since. Nothing has changed with settings on my PC.

Don't have ANY network optimizer programs on my PC either haven't for months. I'll do a malware check I guess but just strange it works perfectly fine with obs32 but not obs64.
 

GrathiusXR

New Member
Done both of what you said. Still have the same problem. Not sure why it's crashing when I go to close the program nor the BrowserSource not loading. Anything in my 2 log files I posted that could help?
 

R1CH

Forum Admin
Developer
The crash you experienced is due to low memory limits of 32 bit programs, so the 64 bit should fix it. No clue why the browser source isn't working there though. If you want to stop by the community chat I could take a look over teamviewer or similar, I've seen something similar that affected OBS Classic.
 

GrathiusXR

New Member
Thing is is that it's my 64bit version crashes. 32bit works flawlessly which is weird. I'll be in Community Chat speak there.
 

R1CH

Forum Admin
Developer
This was solved, problem was caused by the Killer Networking software suite. Uninstalling and reinstalling driver-only fixed it.
 
Top