Application hangs and stream disconnects; no crash report

[SaveMeJebu5]

I want to diagnose this issue, however, occurrence is not consistent but has occurred 2 out of 4 streams to Twitch.tv; once after three hours, and a second time after just 15 minutes. I was using Google Meet at the same time, and streaming that - also worth noting I am grabbing the audio feeds using Voicemeeter and virtual routing. This issue did not occur while streaming live to Facebook, but then again I also wasn't using Meet at the same time - so I wonder if it's related to that.

Also it would appear that OBS is not actually "crashing" (and so, no crash log created) - but the behavior I am experiencing is the OBS app hangs (windows grays out and I can't click anything) and soonafter the stream disconnects. Any help would be appreciated. Attached log.

Added info: I am streaming over wired connection. No dropped frames are reported. I am using an aftermarket gigabit network adapter card, not the onboard one for my motherboard. This issue occurred when using a single monitor, and when using two monitors.

 

[SaveMeJebu5]

Thanks for the reply

run obs as admin

OK I set the application shortcut to run as admin.

deinstall defender make the job

"Defender"? Oh, you must mean the antivirus software. I will definitely try disabling if problem isn't solved by these steps.

AAC encoder

I had iTunes installed prior to this issue, but it was 32-bit. Installed Quicktime 7 just now, which includes "Apple Application Support" - this seems right. However, I noticed that this was also 32-bit version (the only one I could find), and discovered that Apple no longer offers support for Quicktime for Windows! Ok, so the instruction article you linked is a bit out of date, but that's fine: I went searching for the msi file mentioned, and that led me to this article https://discussions.apple.com/thread/7516836 which explains "It [AppleApplicationSupport64.msi] isn't available as a standalone download." So I went ahead and uninstalled iTunes 32-bit, so I could get iTunes 64-bit - which then prompted me to install iTunes again (lol). Long story short: I think this may have fixed the AAC encoder issue, but figuring out how to do anything was rather janky and the steps here on obsproject probably could use some updating.

windows event list ?

I was able to find the following error which coincides with the issue I experienced:

The program obs64.exe version 26.0.2.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.
Process ID: 4ac8
Start Time: 01d6bdca4dee401d
Termination Time: 9
Application Path: C:\Program Files\obs-studio\bin\64bit\obs64.exe
Report Id: d936df92-cc37-407f-a727-fd79b13cf1d6
Faulting package full name:
Faulting package-relative application ID:
Hang type: Unknown

Looking at the Security and Maintenance control panel, I found this:

Source: OBS Studio
Summary: Stopped responding and was closed
Date: ‎11/‎18/‎2020 12:02 PM
Status: Report sent
Description: A problem caused this program to stop interacting with Windows.
Faulting Application Path:    C:\Program Files\obs-studio\bin\64bit\obs64.exe

Problem signature
Problem Event Name:    AppHangB1
Application Name:    obs64.exe
Application Version:    26.0.2.0
Application Timestamp:    5f7ca479
Hang Signature:    cec4
Hang Type:    134217728
OS Version:    10.0.19041.2.0.0.256.48
Locale ID:    1033
Additional Hang Signature 1:    cec4bf5f17524adcb368cca65266ac8e
Additional Hang Signature 2:    5831
Additional Hang Signature 3:    58313ebefafb9f6bb63aa663bcdc8dad
Additional Hang Signature 4:    cec4
Additional Hang Signature 5:    cec4bf5f17524adcb368cca65266ac8e
Additional Hang Signature 6:    5831
Additional Hang Signature 7:    58313ebefafb9f6bb63aa663bcdc8dad

Extra information about the problem
Bucket ID:    3de190057d3be8d1e22ebaa4e0fb04ad (1310189758923343021)

 

[SaveMeJebu5]

Think so!

Thanks for the help. After the steps I took last week (described above), I was able to successfully stream without issue today. Will report back if another issue comes up.

 

[Lawrence_SoCal]

11:46:04.443: Running as administrator: false > run obs as admin

Note for all - the OBS authors/senior folks on this site do NOT support this recommendation
Running OBS as Admin is ONLY needed if running into CPU/GPU contention issues.. otherwise, bad security practice and unnecessary (ie no upside, only downsides). If you don't have resource contention and running as admin does resolve an issue, then best to figure out specifically what the issue is (vs the sledgehammer as a fly-swatter approach that is running as admin)
@SaveMeJebu5 - see my other post, in case related to Chrome browser window in background not rendering (having nothing to do with OBS)

 

[SaveMeJebu5]

Note for all - the OBS authors/senior folks on this site do NOT support this recommendation
Running OBS as Admin is ONLY needed if running into CPU/GPU contention issues.. otherwise, bad security practice and unnecessary (ie no upside, only downsides). If you don't have resource contention and running as admin does resolve an issue, then best to figure out specifically what the issue is (vs the sledgehammer as a fly-swatter approach that is running as admin)

Ah, true - perhaps the AAC support was the real fix, and the Run as Admin part was unnecessary. I guess I should see if running as usual causes the issue to return.

@SaveMeJebu5 - see my other post, in case related to Chrome browser window in background not rendering (having nothing to do with OBS)

Yes, saw that and replied, but now I wonder if these issues may actually be related (IE it seems neither has much to do with OBS per say). Hmmm..

 

[R1CH]

Are you manipulating display capture sources when this happens?

 

[SaveMeJebu5]

Are you manipulating display capture sources when this happens?

edited (forgot quote)

No, but I recall I was changing focus between apps around the exact moment OBS froze. OBS was on display (monitor) 1, Meet was on display 2. I also recall I had OBS full-screened, while Meet was in windowed mode on the other display.