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: memory leak (Read 4739 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

memory leak

i am getting a huge memory leak, even after i deleted foo_tunes as picmixer suggested in this thread
but it just happened again, what else could cause this
i am running these 3rd party components : columnsui, foo_TLB, foo_audioscrobbler, foo_viral,

heres a screeny of how much foobar is using

memory leak

Reply #1 –
You're using 2 components I've never even heard of, but foo_audioscrobbler has been known to act up in the past, so I'd try removing that one first.

memory leak

Reply #2 –
Same here. Could you please inform us about the nature of foo_TLB and foo_viral.  I have really never heard of them.

Audioscrobbler has been known to cause problems in the past, but the newest version seems to have improved somewhat in that area.

Also never heard of audioscrobbler causing memory leaks so far. But you never know.

memory leak

Reply #4 –
Thanks a lot for the info. Now that you mention it foo_viral does ring a bell somehow.

Could you maybe do us a favour and remove those components one by one and see when the memory leak dissapears?

Simply remove one of them, run fb2k for quite a while. Check if the leak is still there. Then remove the next, check again if the leak is still there, and so on.

This would really help us to figure out what exactly is going wrong here.

EDIT
Oops sorry. Just read your last line. Must have overlooked that before.  Seems it won't be that easy for you to verify this indeed.

memory leak

Reply #5 –
I'm generally pretty good at avoiding memory leaks, and I haven't had any reported before, so my money's on one of the other two...

memory leak

Reply #6 –
no its def AS, i had removed the other two and was only running AS and the memory leak happened again

memory leak

Reply #7 –
OK, what OS are you running? This may or may not have something to do with the fact that it's statically-linked with the VC++ 7.1 runtimes.

memory leak

Reply #8 –
i am running Win XP Pro SP1

memory leak

Reply #9 –
Quote
foo_viral : Viral Sound creates a now playing image for forum signatures etc., it just sends the track info to a webserver[a href="index.php?act=findpost&pid=235272"][{POST_SNAPBACK}][/a]

If that's the same thing that foo_winamp_spam does, then you might try it instead -- I haven't had a lick of problem with it.
------- Rick -------
--------------------

memory leak

Reply #10 –
i had a huge memory leak as well....
i have no plugins that dont come with foobar, and i really dont use any of them
i have windows xp home
and the only thing i can think of that i dont normally do with foobar is that i left it paused on a song, but i duno i usually just dont leave it running

so if anyone can figure anything out that would be greatly appreciated

memory leak

Reply #11 –
Quote
Audioscrobbler has been known to cause problems in the past, but the newest version seems to have improved somewhat in that area.
[a href="index.php?act=findpost&pid=235270"][{POST_SNAPBACK}][/a]

I don't have any problem with Audioscrobbler here since last version 

memory leak

Reply #12 –
Hi, I have a mem leak here too, fb2k v0.8.3, while transcoding files from mp3/wmal to ogg vorbis. Current fb2k RAM usage is 552MB after 700 files transcoded. Running on WinXP Pro SP2, WMP10 installed, using the plugins shipped with fb2k.