Stream dropping to 0Kbs then 20.000kbs

[Chocoferu]

Hi! I'm having this random problem that usually occurs once per stream at a random time.
It drops to 0kb/s for a couple of seconds, then goes to over 20.000kbs and slowly downs to the usual 6000kbs, but it destroys the stream some seconds and people are unable to watch me and they have to refresh the page to make it work again.

The stream started at 21:44 and the problem was at 23:33 aprox, but logs doesn't show anything at that time, but there are TONS of "streamelements" errors during the stream, wich is weird!

I changed some sound stuff that day, can it be that?

Thanks a lot!

 

[Chocoferu]

I could use some help ;_; I'm really desperate with this problem. I did everything;
Format PC and install everything again: failed
Disable all useless audio sources: failed
Changing all image sources: failed
Stop all the antivirus and literally turning off the firewall: fail

It happens always, randomly on any stream and just once, sometimes breaking my sound. 0kb/s for a couple of seconds, then 20k+ like OBS was trying to recover all the data lost.
PS: doesn't seem like an internet/ethernet problem, btw

 

[konsolenritter]

I wonder if it doesn't happen more often. To be honest, your cpu is an i7-5800 series and i can see tons of plugins and filters set even in the video section. You have a capable gpu, i think. But there are alot of tasks that stick with the cpu still. And - as you noted already - there are a huge heap of moanings and error/warn msgs by different parts, that have to be handled, too. Nearby 500 memory leaks noted during runtime. There are network bound sources (two NDI sources, at least), and massive use of web-sockets too. So there are much things plaited into the strong timing structure within the obs'es threads. A wonder that only 2 frames stalled due to rendering lag. Astonishing. =)

Within the graphics thread there is "tick_sources" maxing out once by 9,7 seconds. That could be your special noted problem (fits in so far: compositing is delayed once, then the encoder gets flooded with subsequent frames to handle. It seems that at least one of the sources couldn't be collected before. Something is blocked or lagged deadly. Due to your very complex setup its difficult to isolate that.
Did you had a look into the cpu usage that moment?

Try to start with a lean profile/scene setting and get rid of that error messages and warnings. It means additional cost for cpu and i/o subsystem. Personally i think you had a lot of luck so far.

(Breaking the sound fits into the issue at all. Sound is rendered by cpu completely.)

 

[Chocoferu]

snip

I see, thanks!! So the best thing to do is to start a new profile and test scene by scene, right? Maybe there's one web browser that is messing everything, because I have tons and tons of Streamelements errors D:

I guess there are some web browsers that work on the background even if the scene isn't even active. Can they work on the background if they're not even on any scene? I mean, OBS always saves my sources just in case I need them sometime, can this be possible?

Thanks a lot for your help! If I ever solve this, I'll make a post warning people, because this isn's a common issue and I know there are ppl with this kind of problem D: