Memory Leak?

[RichG]

Hi Jeremy,

I think there may be a memory leak in the latest version (2.3.30.1).

I had a rare system lock up just now after using browsing Muso intensively for maybe an hour including viewing LastFM and Wikipedia entries. The whole machine became very unresponsive and when I managed to get into Task Manager it was showing Muso as using over 5.5 GB RAM. Shortly after the machine completely froze and I had to use the reset button (which is something a try to avoid as much as possible).

I've started up again with just Muso and this browser running and I can see Muso ram use creeping up again (it's at about 1.5 GB after about ten minutes) and heading steadily upwards.....

[musoware]

Hmm OK thanks for that info - I can't think of anything specific to any recent version that would have made a difference to memory consumption. How many albums and tracks do you have in your collection?

[RichG]

Roughly 4800 albums and 66,000 tracks.

[RichG]

The current instance of Muso is now up passed 2 GB and I've not touched it since the original post.

[MDE]

Which windows version?

[RichG]

Windows 7 64bit

[MDE]

Hmm. I had similar problems when I used Vista, but subsequently W8.1 and W10 have been much better. I'm still on Muso 2.3.29 though.

[musoware]

The current instance of Muso is now up passed 2 GB and I've not touched it since the original post.

That's curious, music is playing though? Which player? Is remote active? Pivotviewer?

[RichG]

The player is a RaspberryPi running Squeezelite/piCorePlayer via LMS.

Stopping playback doesn't stop the memory usage increase - currently up to 3GB

[musoware]

The player is a RaspberryPi running Squeezelite/piCorePlayer via LMS.

Stopping playback doesn't stop the memory usage increase - currently up to 3GB

That is excessive, my db is almost as big as yours and my memory usage as reported by Task Manager is about 350Mb, and fairly stable.

What view do you have it on when it increases rapidly? Or does that matter?