Prevent non native text tracks from leaking cuechange event listeners #2849
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Due to a new updateDisplay function being generated on each invocation of the textTracksChanges function within emulateTextTracks of Tech, the cuechange event listener which called updateDisplay was not getting removed when looping through text tracks. This created a leak where updateDisplay could be called many times on a single track cuechange event.
An example of this can be seen by running the following:
When a cuechange is reached (the first being at 1 second), texttrackchange will be triggered 3 times (one for each set of track.mode).
This change moves the updateDisplay function outside of the textTracksChanges function, so that it will not be regenerated on each call of textTracksChanges.