-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
fix: Destroy preload managers on player destroy #6576
Merged
avelad
merged 1 commit into
shaka-project:main
from
theodab:autoDestroyPreloadManagerBranch
May 10, 2024
Merged
fix: Destroy preload managers on player destroy #6576
avelad
merged 1 commit into
shaka-project:main
from
theodab:autoDestroyPreloadManagerBranch
May 10, 2024
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
A PreloadManager can only be used on the Player instance that created it. That means that once that Player instance is destroyed any PreloadManagers it made are basically useless, so they should be automatically destroyed too.
d114005
to
b256e99
Compare
avelad
approved these changes
May 10, 2024
Incremental code coverage: 90.00% |
joeyparrish
reviewed
May 10, 2024
} | ||
} | ||
await Promise.all(preloadManagerDestroys); | ||
this.createdPreloadManagers_ = []; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would have preferred this above await
. Probably not crucial, but ideally you would empty that array right after initiating all those promises, rather than after they complete.
theodab
added a commit
to theodab/shaka-player
that referenced
this pull request
May 11, 2024
Based on a comment on shaka-project#6576
theodab
added a commit
that referenced
this pull request
May 11, 2024
This could be relevant if destroy() is called multiple times in a row. Based on a comment on #6576
avelad
pushed a commit
that referenced
this pull request
May 13, 2024
A PreloadManager can only be used on the Player instance that created it. That means that once that Player instance is destroyed any PreloadManagers it made are basically useless, so they should be automatically destroyed too.
avelad
pushed a commit
that referenced
this pull request
May 13, 2024
This could be relevant if destroy() is called multiple times in a row. Based on a comment on #6576
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
priority: P1
Big impact or workaround impractical; resolve before feature release
status: archived
Archived and locked; will not be updated
type: bug
Something isn't working correctly
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.
A PreloadManager can only be used on the Player instance that created it. That means that once that Player instance is destroyed any PreloadManagers it made are basically useless, so they should be automatically destroyed too.