System: Windows XP HE, Service Pack 1, all current patches installed
Sony Vaio Notebook, mobile AMD Athlon 1.6 GHz, 256 RAM

latest foobar2000 beta = v0.8 beta 7
DSPs: Volume Control, Crossfader, Gap Killer, Skip silence, Advanced
Limiter

foobar2000 seems to require/use quite an amount of system ressources, i.e. RAM.
I have been noticing this for quite some time now.

The amount of RAM used when

- idle (not playing): around 14 MB
- active (playing): around 20 MB

Compared to WinAmp 5.01:

- idle (not playing): around 10 MB
- active (playing): around 11.5 MB

Any ideas anyone?

Thank you

Please read FAQ.

This is very odd. When it is playing it is only using 7.2MB of RAM. Did you try uninstalling the old version, or just deleting anything unnecassary, and reinstalling the program? These are still beta versions so there might be something related to that. When in doubt, though, use the latest stable version.

How big is your database.foo file? I wonder if larger databases made Foobar take more memory.

--Grant

Well, first of of course I read the FAQ and of course found this hint.
I did try and remove - the very few - DSPs but that doesn't change much.
Secondyl DSPs only become 'active' while playing but not necessarily in idle mode.
Anyway - what happens _WITHOUT ANY_ DSPs is that the memory used in idle mode remains the same: around 14 MB. While playing the amount is decreased from the 20 MB WITH DSPs to 16 MB. Well...



I did this when I 'switched' to version 0.8 from 0.7 - the memory usage 'problem' remained the same.



It is actually rather small, around 360 KB.

Any other ideas?

How many files in your playlist/how many playlists?

Also:

What UI are you using?

Are you using foo_looks to control foobar?

This is a touchy subject by the way, as it has been proven many times that foobar has a very small memory footprint on its own.

My stats are this for instance:

As was said just above, how long did you watch the usage? I think Spase summed it up pretty well in that the usage IS high when the player is loaded by drops after it is running for a few minutes. Hopefully we can figure out what is going on as it should not be running nearly that high. Good luck to you and hopefully someone hear will help you figure out what is going on.

hey i have the same problem.
but not only is the memory usage high, but the CPU Usage is high ~42
and the mouse pointer becomes choppy while playing.

my system config is

Win XP Pro SP 1
Intel 800 MHz
128 MB Ram

and the foobar v8b6
columns UI

DSP's used:
channel seperation
convolver
equilizer
volume control

but my database is 4.05 MB
is this causing the problem?

I've had this problem since v7.7
the earlier versions were fine!!!

Quick, easy way to decrease memory footprint and decrease CPU load: delete unused components and disable DSPs. If you've installed the Special installer, there's a memory cost for all the components. If you're using convolver and EQ, they're both CPU intensive. If you install the program with all the extras, there's a cost for it.

It would be great to be able to remove componoents through the UI (just like winamp). It is not that easy to figure out what a component is just by its file name.

What the hell are you talking about? If you can't figure that out, well...

its funny how we point a finger first at someone else rather than ourselves!!!:-)

I downloaded v8b7
the cpu usage came low, but not low enough.

But suprises when i removed convolver from the DSP List!!!! :-)
CPU usage came down to 5 and memory usage came down to ~2MB!!!

Hey that feature is actually quite nifty.

Of course if it requires hacks, then I'd rather not have it.

No hacks, but it'd have to be built into the actual executable. It couldn't be implemented as a component. (Well, technically it could, but it would be a very bizarre, very unintuitive implementation.)

those foo_xxxx.dll are hard to decipher.

who would know that foo_masstag.dll was for mass tagging
foo_flac.dll was for flac support ..

too cryptic .. but foobar tells you ..

Preferences > Componets > list off all the componets and the DLL name.

I just checked online and RAM is 13 cents a meg on Newegg. Rather then spend all this time argueing and troubleshooting over 60 cents worth of memory, perhaps you should consider upgrading.

And if you're really that concerned about memory usage, you shouldn't even be running Windows at all. I can run Firebird with multiple tabs, xmms, xchat, gaim, and several terminal windows in Linux without using any swap at all (with 512 MB memory).

I don't really know if this is the correct place to bring this point up but while transcoding from wv to m4p using Foobar and Nero, cpu usage leaps to 100% (taskmanager) and more often than not the computer freezes.

Nothing else is running and as far as I know there are no viruses, spyware etc (Norton, adaware and spybot all updated).

Any ideas?

1Gb Ram
Duron 1200
Xp pro SP1
Foobar beta 6 (I understand the significance of beta).

auldyin

if your computer freezes while working at 100%, then your cpu or hardware componets has serious stability issues. you should prolly run memtest to test your memory and use a variety of programs that stress your cpu to check for stability. Prime95 or Toast.

i just checked on this.
(beta7-special with empty playlist and none additional plugins edit: forgot foo_syfm )

in this order:

fresh start: ~13,7mb
send fb to tray: ~700kb
restore: 1,6mb

after adding 3 albums to pl (42 tracks): ~9,1mb
send to tray: ~700kb
restore: ~2mb

hit play: ~7,7mb
send to tray: ~2,7mb
restore (still playing): ~3,7mb


seems alright to me.

ROFL!

If your post was meant to be sarcastic, then I agree with you.

what is foo_stfu.dll? (found in normal installer)

I know "foobar tells me", but i can't do anything to the dlls while foobar is still running, right?

And there is a message at the page, "Note that the above list contains only components that report their name / version info." So there may be something missing.

The seekbar.

Search the changelog for "STFU".

zZzZzZz put it there so everyone who was screaming about a seekbar would shut the f*** up (remember that the early versions of FB2K didn't have a seekbar).