The previous huge leak is gone, but I think I have found another.
I bring up Parallels in Coherence mode and run Rhapsody ( a subscription
music service; there is a free trial/mode if you want to duplicate the leak).
While playing music I see the memory grow, not nearly as fast as the old one,
but 1 meg every few minutes. The activity monitor under OS X will
show all this memory but window's task manager will not. If I kill Rhapsody
the memory does not get reclaimed. So, I don't think it is a Rhapsody leak.
Since this is an audio app it could be related to delivering audio from windows
to OS X, but my gut feeling is that this is a networking leak. The way Rhapsody
works (I am a developer working for the company that makes it) is that each
time a song begins it will download it at a rate faster then what it plays at, near
the end of the song there won't be anything left to download, so there will be
no network activity until the next song needs to get pre-fetched. This is exactly
what I see the memory doing, going up at the beginning of a song and then
not go up at all until about the time the next song is pre-fetched over the
network. If this was an audio leak then I would expect to see the leak go up
steadily over time since the audio never stops.
Anyway, hope this helps, let me know if you want more info.
--greg.
I bring up Parallels in Coherence mode and run Rhapsody ( a subscription
music service; there is a free trial/mode if you want to duplicate the leak).
While playing music I see the memory grow, not nearly as fast as the old one,
but 1 meg every few minutes. The activity monitor under OS X will
show all this memory but window's task manager will not. If I kill Rhapsody
the memory does not get reclaimed. So, I don't think it is a Rhapsody leak.
Since this is an audio app it could be related to delivering audio from windows
to OS X, but my gut feeling is that this is a networking leak. The way Rhapsody
works (I am a developer working for the company that makes it) is that each
time a song begins it will download it at a rate faster then what it plays at, near
the end of the song there won't be anything left to download, so there will be
no network activity until the next song needs to get pre-fetched. This is exactly
what I see the memory doing, going up at the beginning of a song and then
not go up at all until about the time the next song is pre-fetched over the
network. If this was an audio leak then I would expect to see the leak go up
steadily over time since the audio never stops.
Anyway, hope this helps, let me know if you want more info.
--greg.