Closed FalcoGer closed 1 year ago
There have been a few memory leaks that should now be fixed (especially one that would waste tons of memory just by having the UI visible). While I can still "reproduce" this with the procedure you indicated, the memory usage stops climbing after a few attempts, so I don't think it's an actual memory leak.
In addition, I ran the program (after the leak fixes) through valgrind massif and it seems to properly clean up resources after an alarm is stopped.
Thus, I think this can now be closed.
I have left the alarm applet on for some time and using it for a bit now. After a few days it now uses 280+MB of ram. I have 5 timers and 1 alarm, all of which use the same 12MB mp3 file.
Top output
After setting up a 1 second timer alarm and playing the sound file a few times, the memory consumption went up by roughly 100kB every time I pressed the stop alarms button.