I see this bug was marked fix already, but I thought I would add this in case it was relevant later on.
My system had the same issue where it would eat all the RAM and then explode after a while. This happened while just playing audio files (mp3 or ogg)
What I've always noticed was this RAM leak occurs when it's "buffering". I play audio files over a NFS share and when the NFS server is asleep, you play an audio file, VLC has to wait to buffer. While in the "buffering" state, the RAM usage and CPU will max out. Once th NFS starts streaming it goes away and the file plays. But sometimes when you are moving around on the audio file (using the cursor to skip around), it always buffers and sometimes that's when it would go into a RAM leak state.
My system specs were Mandriva 2010.0 x64 + 16GB RAM, running VLC 1.0.4 (yeah, old version, but it appears the bug has been around for a while)
So while it might be audio plugin related, I wonder if something in the buffer code was also causing an issue or if will be an issue in future versions to be triggered in some unknown way.
I see this bug was marked fix already, but I thought I would add this in case it was relevant later on.
My system had the same issue where it would eat all the RAM and then explode after a while. This happened while just playing audio files (mp3 or ogg)
What I've always noticed was this RAM leak occurs when it's "buffering". I play audio files over a NFS share and when the NFS server is asleep, you play an audio file, VLC has to wait to buffer. While in the "buffering" state, the RAM usage and CPU will max out. Once th NFS starts streaming it goes away and the file plays. But sometimes when you are moving around on the audio file (using the cursor to skip around), it always buffers and sometimes that's when it would go into a RAM leak state.
My system specs were Mandriva 2010.0 x64 + 16GB RAM, running VLC 1.0.4 (yeah, old version, but it appears the bug has been around for a while)
So while it might be audio plugin related, I wonder if something in the buffer code was also causing an issue or if will be an issue in future versions to be triggered in some unknown way.