apollo4244
New Member
I'm in the process of helping a streamer who's Windows system keeps running into a Tcpip error 4227 (dynamic port exhaustion issue) after a couple hours of streaming every time.
Since it seems like OBS itself or a running plugin is involved in this whole thing I'd like to ask for help here.
I was able to track down the port exhaustion being some kind of loop going on with mDNS/TCP traffic on (port 5354) through loopback address from chrome.exe (Google Chrome) and mDNSResponder.exe (Bonjour service). Microsoft Edge shows the same behavior btw.
Chromium browsers seem to have some kind of Google Cast bs built in which cannot be disabled (anymore).
The interesting thing though is this loops starts to being triggered by obs.exe itself. As soon as we startup OBS it seems to send out mDNS traffic of some kind and Chromium in combination with Bonjour do their thing about until dynamic TCP exhaustion happens.
The whole process takes a couple hours until exhaustion, but during this time everything on the PC slows down more and more and sometimes processes crash completely.
If we shutdown just one of each, OBS, Chromium or Bonjour, things calm down again or don't come up at all.
I could also recreate the exact same port exhaustion on my very own Workstation just by enabling Bounjour service, running either Chrome or Edge and startup OBS (but this doesn't mean either Bonjour, Chrome or OBS is the source of the issue).
But I wasn't able to reproduce it on another PC yet!
Our solution for now is to disable Bonjour service but he's somewhat restricted not having it available for streams. And since I don't have high hopes to get any support from Apple or Google soon I'm asking for help here.
What I want to try is to find out if whatever OBS triggers to do such mDNS requests.
I'd like to know if it's a plugin we both use or OBS itself.
Maybe there are any additional logs or something to be enabled to get an idea of what's going on or anyone already knows what to search for(?).
The attached log is from my Workstation.
I'm able to reproduce this behavior any time running Chrome, Bonjour and starting up OBS.
But Chrome needs some time until it starts doing casts. Regarding to my own findings opening YouTube for example can speed up this.
Appreciate any help!
Since it seems like OBS itself or a running plugin is involved in this whole thing I'd like to ask for help here.
I was able to track down the port exhaustion being some kind of loop going on with mDNS/TCP traffic on (port 5354) through loopback address from chrome.exe (Google Chrome) and mDNSResponder.exe (Bonjour service). Microsoft Edge shows the same behavior btw.
Chromium browsers seem to have some kind of Google Cast bs built in which cannot be disabled (anymore).
The interesting thing though is this loops starts to being triggered by obs.exe itself. As soon as we startup OBS it seems to send out mDNS traffic of some kind and Chromium in combination with Bonjour do their thing about until dynamic TCP exhaustion happens.
The whole process takes a couple hours until exhaustion, but during this time everything on the PC slows down more and more and sometimes processes crash completely.
If we shutdown just one of each, OBS, Chromium or Bonjour, things calm down again or don't come up at all.
I could also recreate the exact same port exhaustion on my very own Workstation just by enabling Bounjour service, running either Chrome or Edge and startup OBS (but this doesn't mean either Bonjour, Chrome or OBS is the source of the issue).
But I wasn't able to reproduce it on another PC yet!
Our solution for now is to disable Bonjour service but he's somewhat restricted not having it available for streams. And since I don't have high hopes to get any support from Apple or Google soon I'm asking for help here.
What I want to try is to find out if whatever OBS triggers to do such mDNS requests.
I'd like to know if it's a plugin we both use or OBS itself.
Maybe there are any additional logs or something to be enabled to get an idea of what's going on or anyone already knows what to search for(?).
The attached log is from my Workstation.
I'm able to reproduce this behavior any time running Chrome, Bonjour and starting up OBS.
But Chrome needs some time until it starts doing casts. Regarding to my own findings opening YouTube for example can speed up this.
Appreciate any help!