Bug 5630 - Generating a MusicIP Playlist appears to leak memory in slim.exe
: Generating a MusicIP Playlist appears to leak memory in slim.exe
Status: RESOLVED WORKSFORME
Product: Logitech Media Server
Classification: Unclassified
Component: MusicIP
: 7.0
: PC Windows XP
: P2 normal (vote)
: ---
Assigned To: Squeezebox QA Team email alias
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-09-30 19:26 UTC by Doug Williams
Modified: 2007-10-01 19:15 UTC (History)
0 users

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Doug Williams 2007-09-30 19:26:54 UTC
SC is running on Windows XP.
Browser is running on Windows Vista.
MusicIP 1.7.1 GUI running on Windows XP, minimized

MusicIP settings in SC Server Settings is set to generate an 80 song playlist.

remote desktop to the server (XP) box and start the Windows Task Manager
Size the RD windows so that the Task Manager fills the window and you can work on the local (Vista) desktop.

Note the memory usage of the slim.exe process on the XP box.

In the SC browser on the Vista box click on My Music, Albums
Mouse over an Album and hit the "M" icon.
Note that the slim.exe memory usage grows significantly and stays there.  The growth is approx. 1meg. of usage.  Also note that it doesn't happen every time - potentially varying based on the "difference" between the album generating from and the last album generated from.

I know that the Windows Task Manager is notorously off, but usually it is good enough to be able to spot gross trends with...

Also, playing the MusicIP playlist does cause the memory usage of slim.exe to jump up and down but seems to be trending upwards overall - although very, very slowly.  It goes up or down with each song change but seems to never quite get back down to where it was when I started playing.

Here are the memory usage numbers for playing songs (no other activity from the browser, etc.):
114460 after song 1 has started
115280 after song 2 has started
114480 after song 3 has started
114576 ...
115164 ...
114648 ...
115060 ...
114596 ...
114808 ...
115350 after song 10 has started

This is small enough it is PROBABLY due to Windows Task Manager reporting errors, but just in case...
Comment 1 Doug Williams 2007-10-01 19:15:18 UTC
Not able to reproduce this with the 10/1 build.