Skip to content

Commit 7a50ed7

Browse files
committed
[FragmentLoader] Fix edge case for LOADING_IN_PROGRESS
Unsure if this is correct fix, but there was an edge case where leveling up immediately after first (test) Fragment caused infinite loop if that level up Fragment was determined to take too long to load, which is a strange considering that metrics determined that it was possible to load that Fragment.
1 parent 858d5c4 commit 7a50ed7

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

src/com/pivotshare/hls/loader/FragmentLoader.as

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -372,7 +372,7 @@ package com.pivotshare.hls.loader {
372372
* loading to determine if we should stay at current bitrate.
373373
*/
374374
case LOADING_IN_PROGRESS:
375-
if(_hls.autoLevel && _fragCurrent.level) {
375+
if(_hls.autoLevel && _fragCurrent.level && _fragmentFirstLoaded) {
376376

377377
// monitor fragment load progress after half of expected fragment duration,to stabilize bitrate
378378
var requestDelay : int = getTimer() - _metrics.loading_request_time;

0 commit comments

Comments
 (0)