-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve abandon request rule #3840
Comments
Additional comment: |
I got the same observation in another test compared to yours. |
Some initial changes and fixes here: #3944 |
This issue has been automatically marked as stale because it has not had recent activity. However, it might still be relevant so please leave a short comment if it should remain open. Otherwise the issue will be closed automatically after two weeks. Thank you for your contributions. |
This issue has been automatically closed because no further activity occurred. If you think this issue is still relevant please reopen it or contact @dsilhavy. Thank you for your contributions. |
Addressed in #4369 |
Environment
Steps to reproduce
Please provide clear steps to reproduce your problem
open reference test page
Open options and enable AbandonRequestsRule
Load the content on netwrok with high bandwith
wait for buffer to be full at highest quality
open browser dev tools and limit network for example to 500kb/s
If the bug is intermittent, give a rough frequency if possible
Observed behavior
Once a segment is abandonned, next segment will still be downloaded at the highest quality
=> the measured bandwith of the abandonned segment is not considered when determining next quality
Console output
Expected behavior
If a segment is abandonned, next segment shall be downloaded at a lower (or at the lowest?) quality
The text was updated successfully, but these errors were encountered: