Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[hyslopc]

I highlighted my entire music collection (around 6000 files), and asked MJ8 build 272 to analyze replay gain on all of them (skipping analyzed files).  It said 4325 needed updating, but after 1159 were done, I hit Stop while one of the tracks was 39% analyzed.  Result was that Stop button went grayed out & cursor changed to an hourglass.  A track was playing in the background, and after it finished, MJ didn't start playing the next track as it should have.  Had to force shutdown from task manager.

[KingSparta]

hard to say...

using slide show?

[hyslopc]

Looks like this is easily reproduceable.  After killing MJ, I started the analysis again.  Exactly the same situation (playing music in background while analyzing replay gain), and exactly same result except that this time I also got a "Virtual Memory warning" from Windows XP, saying that it had to increase the size of the swap file.

So it looks like MJ has a memory leak when analyzing replay gain.

[marty3d]

I can (sort of) confirm the last error (virtual memory). Had this one a couple of builds ago, but managed to finish the analyze. Haven't done a full re-analyze since then, so I don't know how it behaves now.

Once again, thanks for a wonderful/awful product! (Awful because I spend too much time fiddling with artist info/genres/cover art/my own top lists instead of working for real and just listening to the music! )

[hyslopc]

I have played with this a bit more now, and there is definitely a memory leak in the replay gain analyzer.  It leaked 169 megabytes of RAM after analyzing 1577 tracks, which is about 107K per track.  This time I tried it without playing anything in the background, and Stop worked fine, but didn't free up any of the memory.  As soon as I hit "Exit", the memory was freed.  Hope this info helps (is anyone from JRiver following this?)

[KingSparta]

>> and there is definitely a memory leak in the replay gain analyzer.
this may be true

I noticed something happening to memory when analyzing also.

I wonder if replay is going thru a loop and adding each file to the stack, that may eat up memory untill you exit the loop.

[Doof]

I can confirm the memory leak in RGA as well.

4000 songs analyzed and XP was crying by the time it finished.

[Matt]

The leak will be fixed next build.

Hopefully it'll fix the hang as well -- just let us know.

Thanks.

-Matt