fix: Initialize audioplayer instances sequentially#1941
Merged
spydon merged 5 commits intoSep 3, 2025
Merged
Conversation
…ently by awaiting each individual new player creation
Contributor
Author
|
Looks like some doc code from #1928 got pulled into this. If you wanna close that PR, we can continue working in here. |
spydon
changed the title
spydon
approved these changes
Sep 3, 2025
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
When creating lots of audio pools, an "Unknown Error" can happen if too many players are loaded concurrently. By breaking the instantiation of new players into a serially-loaded structure, we can load 100s of players and effectively remove this edge case.
Checklist
fix:,feat:,refactor:,docs:,chore:,test:,ci:etc).///, where necessary.Breaking Change
Related Issues