I know this has been brought up many times before, but I still have yet to find a solution. For some reason both winamp and foobar are taking up like 23-25 megs of memory to run. I just updated my drivers thinking that it might be my hardware (Soundblaster Audigy MP3+ 24bit on WinXP SP1, 1.0ghz PIII with 512 SD RAM), but that still left it the same.

I'm not a freak about memory and resources too much, but my laptop (PIII 1.1ghz 512 SDRAM) runs foobar at 2 megs.

I'm running version 0.7.1 beta4 (Unicode version), I don't have any DSPs enabled at all, and am using 24bit fixed point with Direct Sound.



Any ideas?
TIA

Have you checked the virtual memory column as well? The VM size on my machine has gotten as big as 25MBs...

Right now my VM is at 35M.

It may be due to a large list of detected plugins in the components folder. Try removing all those that you don't need.
I have 512 MB, and FB only takes up 4.5 MB of memory in total.

Or misconfigured database and ghost entries flooding it. Or really huge database (20k or more entries ?).
Or someone's component having memory leaks / taking a lot of memory.

something is seriously wrong...

i have a playlist (divided into 5 via the tabs) with over 27000 tracks loaded (a little over 13000 in database, one list is full database, one list is full database randomized, one is favourites, one is now playing, one is all of my classical music.)...

foobubbla running, as well as foo_looks, many components (foo_dbsearch, foo_addall, foo_contextsort, foo_copynpaste, foo_delete, foo_dsp_mute, foo_dsp_pause, foo_history, pretty much every component) loaded (not all in use tho)

DSP's loaded: Gap killer, Mute, Volume Control, Advanced limiter.

Output using direct sound. 1000ms buffer.

foobar2000 v0.7 beta 6

total memory usage (according to windows task manager... not the most accurate but still...) ~11-14 MB

When i turn off bubbla and minimize foobar it drops to 5 megs.

oh yea system specs are nothign spectacular:

amd athlon XP 1500+ (i think...) 512 pc2700 mb ram, turtle beach santa cruz, windows xp sp1... oh yea also i have a dual soundcard, but i doubt it matters (on board realtek 5ch sound chip... its on the abit AT7)

Either fix your horrible computer, or stop trying to start trouble i'd say.

I Recommend reformat hard drive.

***EDIT***

I was able to push foobar2000 to use almost 30 megs of memory by opening the following (and using the same playlist DSP output etc settings as above).

foo_bubbla
Test DX Visualization
History
DB Search
Console
Simple Spectrum
Test Visualization
Jump to time
Extended Search
Album list

I dont suppose this is your configuration... I would assume 30 MB would be standard for this sort of configuration.

That comment is not at all appreciated. I am not here to "cause trouble" , I am merely looking for some advice as I have been putting up with (for lack of a better term) the high memory use for quite some time now, not posting any questions here for fear of that kind of arrogant remark.

My computer, for the record, is not horrible, there is simply a setting set wrong somewhere, and i was hoping that someone would be able to point out a glaringly obvious or subtly hidden setting that I overlooked or couldn't find.

Like I mentioned in my original post, I'm not a stickler for keeping my resources free for some big mystery application that i am never going to use (like putting plastic on the furniture so it will look new for a mystery guest that never shows up), so it's not that big of a deal. I was simply hoping for a friendly, courteous solution or recommendation. I have enjoyed your posts up until now, spase.


@zZzZzZz:
I just nuked my database and reloaded all my files back in, and my Mem Usage went down to 2,600K. In the time it has taken me to type this paragraph, it has crawled up to 4,776K. I am at work right now on my laptop, and will try this at home. I had no idea that database and album list maintenance could affect the memory so much. Thank you for your suggestion.

@sld:
I removed all unnecessary plug-ins and components, and it did make a slight difference, thanks.

I apologize, must have been doing my best klemm impression.

(apparently 5 hrs sleep, a retarded pop-quiz, and not being counted as present althought being to class on time has an adverse affect on my attitude).

Anyhow i was just making a point.

I would look into your drivers, as you mentioned. Something is obviously leaking... have you upgraded from beta 4 or tried going back to 0.7 standard?

Check windows settings as far as hardware accel, etc. maybe speaker type? (i am not sure if having them set as stereo when they are really 5.1 would make an actual difference or not... I actually have no idea if that setting does ANYTHING)

anyhow, hopefully you won't hate me.

lest i go into hiding with klemm, buschmann, and weithoff (or however you spell his name)

Edit: Smilie added for cathartic effect

Memory leaks tend to continue growing, they don't generally get to ~40mb and just stop.

I know winamp is a bit of a memory gobbler, but ~35mb is a bit much, to have both foobar and winamp taking up 'too much memory' indicates the problem isn't specific to foobar or a particular version of foobar. (My foobar is running bubbla and a bunch of stuff right now taking up 11mb and I feel that is a bit large.)

Are you using directsound with both players, winamp and foobar? Might this be a directsound issue? Try updating directx to the newest from MS?

Interesting that both players have the same anomoly though, that is very unusual. A setting that you change in each? Stream buffer size (http)? Maybe something you set on your main system but not for the laptop?

Could you try a different player? Possibly foobar 0.667 if you have a copy (google for it, I found a link yesterday, but they seem to be vanishing fast). Is it all players doing this to you? Or something Winamp and foobar might share in common (odd as that seems, is it possible)?

I recently had a software problem and one thing that helped me understand better what was going on was uninstalling my software and doing a complete fresh install, then trying things out using the default options. Change options and try it again and again.

If you have been installing things on top of things... Once I installed one of the very early 0.7 beta's on top of an older beta install, and things messed up which a clean install fixed. (Something , to expect with software betas, though with winamp doing it also.. thats certainly different!)

If you have been installing drivers without removing them something similar might happen there. Sometimes when I am having issues I remove devices and their drivers and re-install them fresh after re-booting.. Have had that clear up odd glitches with sound and graphics before.

Try a different soundcard? Physically remove the soundblaster and put some other company's card in (or using onboard sound?) try it then? Maybe its something new in the drivers from 'our friends' at creative labs (soundblaster)?

A really drastic solution is to format and reinstall windows. WIth all the patches, software installs/removals and the complexity of the XP beast itself, trying to track down unusual issues like you seem to be having is often harsher than just redoing it all.

I know how frustrating a problem with a favorite software can be. I do hope you get it figured out.

-> Edit: do you maybe have a 20mb custom format string? <-

Welp, my Foobar, when not playing files runs at 23.5 megs. I chalk it up to the fact that I download all the components available from Case's site and have several of them loaded in.

I hit 27.5megs when playing a song.

It'll hit 40 megs if you run 32-bit fixed point + dithering + convert stereo -> 4.1 + gap killer + crossfeed

But then again, you shouldn't be dithering anything above 16-bits anyway.

I've got 1GB of RAM so I don't really mind (and a 768meg page file). I push it for audio quality rather than lean performance.