strange memory behavior?

I'm writing in hopes that someone can explain xmms behavior to me while
using Netjuke.

When I request a playlist generated by Netjuke (any kind of playlist),
and the playlist starts playing in xmms 1.2.7, I can fire up my memory
utils and watch my available memory go down very quickly.  Memory
returns to normal only after exiting xmms.  As if that isn't spooky
enough, I can then restart xmms (which would of course then have the
previously chosen playlist already loaded) and WITHOUT playing anything
watch my available memory go down as rapidly as if it WAS playing.

This doesn't happen if I play play a bunch of mp3s directly nor when
xmms's playlist is empty, only when xmms is showing a streaming
playlist.  This available memory loss also happens when I stream from
Shoutcast, for example.  So I don't think this is a Netjuke question.

So here's my question: Is this normal?  It sure doesn't seem right but I
admit my knowledge of xmms / streaming / netjuke is limited.  I hope
someone here is smart enough to be able to explain this behavior to me
because I'm really interested in this behavior.  Thanks!




-------------------------------------------------------
This SF.NET email is sponsored by: A Thawte Code Signing Certificate 
is essential in establishing user confidence by providing assurance of 
authenticity and code integrity. Download our Free Code Signing guide:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0028en