You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The AudioPlayer class is exhibiting a memory leak issue due to its strong relationship with the mixerNode, which is a Mixer instance, and the playerNode, which is an AVAudioPlayerNode.
This bug causes unreleased resources and potentially impacts the performance and memory usage of the application.
Steps To produce:
Initialize an instance of the AudioPlayer class
Initialize an instance of Mixer
Attach both the mixer and the player into some engine
Set the player to nil.
Expected Behavior:
The AudioPlayer class should properly release the resources associated with the playerNode and mixerNode instances when they are no longer needed, preventing memory leaks and maintaining optimal performance.
Actual Behavior:
The AudioPlayer class retains strong references to the mixerNode and playerNode instances, even when they are no longer in use. This leads to memory leaks and potentially causes increased memory usage over time.
Crash Logs, Screenshots or Other Attachments (if applicable)
The text was updated successfully, but these errors were encountered:
macOS Version(s) Used to Build
macOS 13 Ventura
Xcode Version(s)
Xcode 14
Description
The AudioPlayer class is exhibiting a memory leak issue due to its strong relationship with the mixerNode, which is a Mixer instance, and the playerNode, which is an AVAudioPlayerNode.
This bug causes unreleased resources and potentially impacts the performance and memory usage of the application.
Steps To produce:
Expected Behavior:
The AudioPlayer class should properly release the resources associated with the playerNode and mixerNode instances when they are no longer needed, preventing memory leaks and maintaining optimal performance.
Actual Behavior:
The AudioPlayer class retains strong references to the mixerNode and playerNode instances, even when they are no longer in use. This leads to memory leaks and potentially causes increased memory usage over time.
Crash Logs, Screenshots or Other Attachments (if applicable)
The text was updated successfully, but these errors were encountered: