search

younesaassila / ttv-lol-pro

TTV LOL PRO removes most livestream ads from Twitch. This is free, don't expect it to be perfect.
GNU General Public License v3.0
1.39k stars 28 forks source link

Increased error rate (error #2000) #179

Closed MisterSheeple closed 1 year ago

MisterSheeple commented 1 year ago

Describe the bug After watching a stream for a few minutes, the stream displays error 2000 and upon refreshing, the stream works fine for a few more minutes before displaying the error again.

To Reproduce Steps to reproduce the behavior:

  1. Install TTV LOL PRO v2
  2. Open a stream
  3. After a little while, the stream stops and displays error 2000 and asks you to refresh the stream.
  4. Upon refresh, the stream works fine for a while until displaying the error again.

Expected behavior No error.

Desktop (please complete the following information):

younesaassila commented 1 year ago

@MisterSheeple Are you using the default proxy?

MisterSheeple commented 1 year ago

@MisterSheeple Are you using the default proxy?

Yes.

younesaassila commented 1 year ago

Could you reproduce the bug with the browser console open (F12) and post a screenshot of the console when error #2000 shows up? Thanks

JohannesKnopp commented 1 year ago

Hi, I am encountering the same issue, also using the default proxy, here a screenshot of the browser console when the error happens: Console Screenshot

OS: Pop!_OS Browser: Firefox 114.0 TTV LOL PRO: 2.0.0 installed as temporary add-on

younesaassila commented 1 year ago

Is this bug still happening? If so, is it happening reliably, like every time? @MisterSheeple @JohannesKnopp

MisterSheeple commented 1 year ago

Is this bug still happening? If so, is it happening reliably, like every time?

I'm having some PC troubles at the moment so I'll get back to you when I'm able to boot again.

JohannesKnopp commented 1 year ago

Is this bug still happening? If so, is it happening reliably, like every time?

Haven't had any ads / errors the last 2 days, but I've also coincidentally installed pi-hole on my end approximately 2 days ago, so I'm not really sure what "fixed" the problem for me (whether it was pi-hole or something else).

DerpDerpingtonIsHere commented 1 year ago

This is still currently still an issue, also happening in chrome as well, and seems at random. Plays anywhere from 3 seconds to 2 minutes then get this error. Something I have noticed though, it does it more when I switch to another tab, not sure if that would have anything to do with it or not or how you would test that.

OS: Windows 11 Browser: Chrome Version: 114.0.5735.134 (Official Build) (64-bit)

zGato commented 1 year ago

This is still currently still an issue, also happening in chrome as well, and seems at random. Plays anywhere from 3 seconds to 2 minutes then get this error. Something I have noticed though, it does it more when I switch to another tab, not sure if that would have anything to do with it or not or how you would test that.

OS: Windows 11 Browser: Chrome Version: 114.0.5735.134 (Official Build) (64-bit)

Tabbing or in any way making the client stop the stream or reset the player will probably trigger error #2000 on peak hours due to limited amout of slots on Chrome. Active connections do not get any issues, but newer may need to click the red "Reload" button until it lets you in.

As always, Firefox users don't have slot limitations. Consider making the change :)

DerpDerpingtonIsHere commented 1 year ago

This is still currently still an issue, also happening in chrome as well, and seems at random. Plays anywhere from 3 seconds to 2 minutes then get this error. Something I have noticed though, it does it more when I switch to another tab, not sure if that would have anything to do with it or not or how you would test that.

OS: Windows 11 Browser: Chrome Version: 114.0.5735.134 (Official Build) (64-bit)

Tabbing or in any way making the client stop the stream or reset the player will probably trigger error #2000 on peak hours due to limited amout of slots on Chrome. Active connections do not get any issues, but newer may need to click the red "Reload" button until it lets you in.

As always, Firefox users don't have slot limitations. Consider making the change :)

Nevertheless, it's still happening even without changing tabs, but see it more when I do. Also, just moving to Firefox doesn't fix the issue for the people who need to use chrome and can't switch. This issue should be at least attempted to be fixed for both browsers.

zGato commented 1 year ago

This is still currently still an issue, also happening in chrome as well, and seems at random. Plays anywhere from 3 seconds to 2 minutes then get this error. Something I have noticed though, it does it more when I switch to another tab, not sure if that would have anything to do with it or not or how you would test that. OS: Windows 11 Browser: Chrome Version: 114.0.5735.134 (Official Build) (64-bit)

Tabbing or in any way making the client stop the stream or reset the player will probably trigger error #2000 on peak hours due to limited amout of slots on Chrome. Active connections do not get any issues, but newer may need to click the red "Reload" button until it lets you in. As always, Firefox users don't have slot limitations. Consider making the change :)

Nevertheless, it's still happening even without changing tabs, but see it more when I do. Also, just moving to Firefox doesn't fix the issue for the people who need to use chrome and can't switch. This issue should be at least attempted to be fixed for both browsers.

Where are you from? (EU/NA/SA...)

DerpDerpingtonIsHere commented 1 year ago

This is still currently still an issue, also happening in chrome as well, and seems at random. Plays anywhere from 3 seconds to 2 minutes then get this error. Something I have noticed though, it does it more when I switch to another tab, not sure if that would have anything to do with it or not or how you would test that. OS: Windows 11 Browser: Chrome Version: 114.0.5735.134 (Official Build) (64-bit)

Tabbing or in any way making the client stop the stream or reset the player will probably trigger error #2000 on peak hours due to limited amout of slots on Chrome. Active connections do not get any issues, but newer may need to click the red "Reload" button until it lets you in. As always, Firefox users don't have slot limitations. Consider making the change :)

Nevertheless, it's still happening even without changing tabs, but see it more when I do. Also, just moving to Firefox doesn't fix the issue for the people who need to use chrome and can't switch. This issue should be at least attempted to be fixed for both browsers.

Where are you from? (EU/NA/SA...)

US.

zGato commented 1 year ago

Add me on discord please: zgato_ Or: zGato | Marc#7399

ipisano commented 1 year ago

I'm having the same exact issue described by the user, I watch twitch exclusively while doing other stuff so I'm always tabbed out of my browser or in another tab. I already tried deleting cookies/cache, reinstalling the extension, resetting uBlock settings (because I used to use VAFT, just in case I didn't clean it up properly) but the error persists. At the moment I'm using an android emulator with a modded app as a workaround, but it's not ideal when gaming because my CPU is already kinda getting a bit grey in the hair compared to my GPU and the performance decrease when running the emulator is evident