Here’s something else that I find very interesting. As I stated earlier in the thread, I get this error when watching UFC events and videos. ESPN+ (Note the Plus) is the streaming platform for the UFC. This means if you wanted to replicate this error, you would need to be logged into ESPN+ and then stream one of the UFC videos that was an exclusive to ESPN+. Of course even the live video feed you see when you log into ESPN+ is exclusive.
Now, here’s where things get interesting. You can also watch streams and/or On Demand videos in their library that aired on one of the ESPN channels. Normal channels on cable or satellite that is. However, you would need to log in with your TV provider. In my case that’s DirecTV. So earlier I went ahead and chose a replay of an even that aired on TV and I logged in with my TV provider. I could see the DirecTV overlay in the video. As I did with the exclusive UFC event videos on ESPN+, I monitored the memory usage in the task manager. I let the video run for about 15 minutes or so. RAM usage never got over 700MB. Compare that to the UFC ESPN+ videos, that running in the same 15 minute period use somewhere in the ballpark of 6 and 8GB.
I’ve very convinced that this particular issue is related to whatever video player tech they are using for those specific videos. Something wrong with the core functionality of the code behind the scenes that is causing a huge memory leak for the browser process that is running. Meanwhile I have a case number with ESPN+ support. I will continue to contact them about once a week to see if there is any progress.