(Huge) Memleak on Fedora 14?
Posted: 09 Apr 2011 10:39
Hi all,
Before I start, I already did some web research and stumbled upon this possibly related thread, but I did not get any help out of it.
So, here is my problem: I use VLC to play some video. I also have a lot of other stuff running, a normal desktop (firefox, thunderbird, you name it). Everything is fine until rsync backup kicks in. VLC starts to lag (which is okay, as rsync may drain the whole available Harddisk I/O for a second sometimes). But VLC also starts to consume more and more memory. Depending on the amount of the rsync I/O load, I have sometimes only 3 seconds to react on that before vlc has my whole 4 GB of RAM allocated, so this can be pretty severe. As it won't stop allocating, the system is dead at that point, despite having swap, cause everything gets swapped and the attempt to run a killall takes too long, vlc has allocated the swap by that time.
I also notice that problem when I have torrents in the background (mainly when they get written to or read from the harddisk), but its not that severe then.
I would like to help at debugging that, I also have the usual debugging tools available (gdb, valgrind) as I am a dev myself, but I have not found an option to limit valgrinds heap yet, as crashing the system would not help when trying to investigate the problem. So if I can give some input, just ask please.
greetings
Before I start, I already did some web research and stumbled upon this possibly related thread, but I did not get any help out of it.
So, here is my problem: I use VLC to play some video. I also have a lot of other stuff running, a normal desktop (firefox, thunderbird, you name it). Everything is fine until rsync backup kicks in. VLC starts to lag (which is okay, as rsync may drain the whole available Harddisk I/O for a second sometimes). But VLC also starts to consume more and more memory. Depending on the amount of the rsync I/O load, I have sometimes only 3 seconds to react on that before vlc has my whole 4 GB of RAM allocated, so this can be pretty severe. As it won't stop allocating, the system is dead at that point, despite having swap, cause everything gets swapped and the attempt to run a killall takes too long, vlc has allocated the swap by that time.
I also notice that problem when I have torrents in the background (mainly when they get written to or read from the harddisk), but its not that severe then.
I would like to help at debugging that, I also have the usual debugging tools available (gdb, valgrind) as I am a dev myself, but I have not found an option to limit valgrinds heap yet, as crashing the system would not help when trying to investigate the problem. So if I can give some input, just ask please.
greetings