Question / Help Frame drop issues started on 0.16.3

[Seak1ng]

So. Ever since I started using OBS Studio version 0.16.3, I've started to have issues with dropping frames.
It started out pretty small, no real issues. But just today, over the course of an hour and a half I dropped aprox. 10k frames, if not more.
Before 0.16.3, and even with OBS Classic, I've never had that issue with my current internet connection, so I'm not sure if it's that but it feels unlikely to me. I checked the most recent log (included) and the only thing that caught my eye was "Memory Leaks: 1". I'm not code savvy, I'm not sure what most of the stuff in the logs mean, which is why I'm asking for help.
Anybody have an idea if it's OBS or just my internet?
(My speed is fine, i have ~5mbps upload)
https://gist.github.com/anonymous/b6169dd5306ada8d5bf002727455ea52

 

[RytoEX]

From your log:

01:17:17.279: [rtmp stream: 'simple_stream'] User stopped the stream
01:17:17.279: Output 'simple_stream': stopping
01:17:17.279: Output 'simple_stream': Total encoded frames: 0
01:17:17.279: Output 'simple_stream': Total drawn frames: 786900
01:17:17.279: Output 'simple_stream': Number of lagged frames due to rendering lag/stalls: 21 (0.0%)
01:17:17.279: [rtmp stream: 'simple_stream'] Freeing 8 remaining packets

That doesn't suggest connection issues, but encoding issues (or perhaps a logging error). Please update to OBS Studio 0.16.5 (or latest), and try again. Then upload a log from a streaming session where you have the issue that you're describing.

The memory leak is a red herring, in this case.

Streaming is less about connection speed and more about connection quality. Try running the Twitch Bandwith Test tool using a Medium Test Duration for your region with a 64k TCP Window Size, and post a screenshot of the results here so that we can see the results.

 

[Seak1ng]

Alright, I tested it first with the settings you said, and the results don't look promising (but i'm not the most knowledgable):

I tried a second time with the TCP Window Size set to Automatic, just to see if there was a difference. There wasn't.
So I'm assuming my connection to the servers is limited to the Bandwidth i'm getting from them? and I should probably set my bitrate properly, but I don't really know I guess.

(Also I don't have the time to start a stream for a length of time so I'm sorry about not getting you new logs)

 

[Seak1ng]

I added an exception for OBS in my firewall to see if that would help anything, and the results were a bit interesting in my opinion:

I understand the whole Quality thing, I want that number to be as high as possible. I couldn't tell you why it's reading 0 across the board.

 

[Seak1ng]

Alright, last update doing what I can to give info:
I set up a small test stream and just let it go for a while. After a few minutes, I loaded up a game just to test.
Zero dropped frames, no issues BEFORE I loaded up the game.
After I loaded a game and just messed around for a small time, suddenly I dropped ~160 frames out of nowhere, and I feel the number would continue to climb if i had kept going. Possibly an encoder issue? Since I didn't have any problems until I started capturing the game.
Here's the log:
https://gist.github.com/anonymous/6247768e8f9b646d0defd4e9864fde45

 

[RytoEX]

The minimum acceptable quality for streaming is 80. Having zeroes across the board is usually indicative of a local problem (hardware/software) or an ISP problem. That frames started dropping once you started the game is probably either coincidence or indicative of your connection's inability to handle an outgoing video stream with changing frames.

 

[Seak1ng]

So, just a quick update (and a warning to some people, more details shortly):
It's practically fixed. I went through troubleshooting with hardware/software and learned something very important;
Killer Network Manager is absolute garbage.
One of the last things I tried in a last ditch attempt was connecting a USB to Ethernet adapter, just to see what happens.
Lo and behold, we have:

So as a warning to those with Killer Network Manager ethernet drivers (necessary for me, with an MSI Z97 Gaming 5 motherboard so I assume the Gaming series or whatnot needs those drivers); don't use it. Find a workaround.

 

[RytoEX]

I've seen a few discussions among staff members about whether or not the Killer Network Manager software was causing issues. This seems to support those theories. Those Twitch Test numbers look much better.

Are you able to stream now?

 

[Seak1ng]

I've been able to stream, but yes, I haven't had an issue yet. I would definitely place blame on the Killer Network Manager software, as that's the only thing I'm bypassing now and it's working beautifully.

 

[RytoEX]

You might be able to install just the drivers for your network card, and then uninstall the Killer Network Manager software suite. Make sure you download the drivers or driver installer before uninstalling the Killer Network Manager software. If you do try this, let us know how it works!