-
Notifications
You must be signed in to change notification settings - Fork 22
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 mpdas, or in libmpdclient? #27
Comments
Thanks for the report. It seems that the song return value is only free'd when a new song is playing. This could be the source of the memory leak. I'll have to do some further research, though. Could you try moving "mpd_song *song = mpd_run_current_song(_conn);" inside the if-statements block for handling new songs and see if the issue persists? |
Aha! I'll do that, and get back when enough playing/non-playing time has
passed...
|
Awesome, thanks for the assistance. I'd do it myself but can't right now.. |
Merged, thanks a lot for the patch + testing! :) |
Thanks, had noticed it was going out of control myself. Might want to do a new release if you feel it's ready, @hrkfdn |
Done! |
I'm a user of mpdas, and observing the process growing slowly over time (it also seems to happen when I'm not playing anything in mpd, but I'm not certain of that).
I've run mpdas through valgrind for quiet some time, with the following result. Have to say I'm no expert in interpreting this. But when reading the relevant code in mpdas (also pasted below), it seems like the right things are done and freed...
The text was updated successfully, but these errors were encountered: