Skip to content
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

Memory leak in SDL_mixer? #28

SDLBugzilla opened this issue Feb 11, 2021 · 0 comments

Memory leak in SDL_mixer? #28

SDLBugzilla opened this issue Feb 11, 2021 · 0 comments


Copy link

This bug report was migrated from our old Bugzilla tracker.

These attachments are available in the static archive:

Reported in version: unspecified
Reported for operating system, platform: All, All

Comments on the original bug report:

On 2007-01-29 12:09:13 +0000, Ryan C. Gordon wrote:


Relevant detail:

"Because this is for unit test, I have the effects on a button press.
So it's very likely that Mix_SetPanning() gets called multiple times.
No other effects were set on that channel.

Here's the flow:

Set volume to MAX
Allocate 2 channels
Load the 2 different chunks (1 on each channel)
Load the music
Play the music (loop forever)
Play chunk 0 on channel 0
(while sfx is playing) Set Panning on both channels to (255, 0)
Halt Channel (passing -1, i.e. halt all channels)
Free chunk 0
Free chunk 1
Mix_AllocateChannels(0) // free all channels
Halt Music
Free Music



On 2007-06-27 15:31:05 +0000, Ryan C. Gordon wrote:

Whoops, this is an SDL_mixer bug, not an SDL bug...


On 2007-07-14 20:40:45 +0000, Sam Lantinga wrote:

Ryan, can you take a look at this for the SDL_mixer 1.2.8 release?

On 2007-07-15 07:43:05 +0000, Ryan C. Gordon wrote:

Looking at this now.


On 2007-07-15 08:17:07 +0000, Ryan C. Gordon wrote:

Created attachment 228
test case.

Here's a test case that triggers the bug. "whoosh.wav" and "" can be just about any file you have laying around your hard drive.


On 2007-07-15 08:57:57 +0000, Ryan C. Gordon wrote:

Fixed in svn revision # 3290.


Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
None yet

No branches or pull requests

1 participant