Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: ReplayGain uses up massive amounts of memory (Read 2970 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

ReplayGain uses up massive amounts of memory

Hi,

I am running foobar 1.1.16b2 on a Windows Home Server system (on which all my media sits).

I am basically trying to apply ReplayGain tags to my whole library of about 16000 tracks. It seems that when I try to do this, foobar begins to eat up all the memory and eventually bombs out with a "bad allocation" error. I've seen it use 1.2 Gb out of the 2 Gb on the system. Then, it actually thinks that the tags have been applied, and data must be reloaded from the tags. The memory actually isn't released until foobar is shut down.

Hope this is helpful!

ReplayGain uses up massive amounts of memory

Reply #1 –
Quote from: wigster on
It seems that when I try to do this, foobar begins to eat up all the memory and eventually bombs out with a "bad allocation" error. I've seen it use 1.2 Gb out of the 2 Gb on the system. Then, it actually thinks that the tags have been applied, and data must be reloaded from the tags. The memory actually isn't released until foobar is shut down.



I haven't seen that, and I've done the same as you........try this external shell program, MP3gain, which does exactly the same.  Read the instructions carefully in order not to "normalize" your files.

http://mp3gain.sourceforge.net/

ReplayGain uses up massive amounts of memory

Reply #2 –
Quote from: wigster on
I am basically trying to apply ReplayGain tags to my whole library of about 16000 tracks. It seems that when I try to do this, foobar begins to eat up all the memory and eventually bombs out with a "bad allocation" error. I've seen it use 1.2 Gb out of the 2 Gb on the system.


I've seen the same thing once as I was RE-scanning with the new algorythm, and it was just a little over 1.2GB as well. As far as I remember, tracks were mixed MP3 and FLAC.

ReplayGain uses up massive amounts of memory

Reply #3 –
Quote from: Sandrine on
I've seen the same thing once as I was RE-scanning with the new algorythm, and it was just a little over 1.2GB as well. As far as I remember, tracks were mixed MP3 and FLAC.


This also happened to me: rescanning with 1.1.6 B2 a whole lot of MP3s + FLACs took all my memory. I had to scan smaller pieces of the library in order to avoid out of memory. Between each scan I also had to close foobar2000, otherwise occupied memory continues growing with new scans.

Also, this thread should be moved in "Support" forum I guess.

ReplayGain uses up massive amounts of memory

Reply #4 –
Quote from: mccarver on
Quote from: Sandrine on
I've seen the same thing once as I was RE-scanning with the new algorythm, and it was just a little over 1.2GB as well. As far as I remember, tracks were mixed MP3 and FLAC.


This also happened to me: rescanning with 1.1.6 B2 a whole lot of MP3s + FLACs took all my memory.


I have mixed FLAC and MP3, but this also happens if I just scan some MP3s. It seems to happen at about 4000 files, whether you do it in batches or not. You have to quit the application and restart in order to clear the memory.
 

ReplayGain uses up massive amounts of memory

Reply #5 –
Fixed in the next version; see this topic.