memory leak wasapi win7?

What process exactly is spiking?  Foobar2000, audiogd, or something else?  Is the processor spiking, or actual 'memory usage'?

Win7 64-bit + foobar2000 + WASAPI here, no memory leak problems. What do you mean exactly by "ram problems"?

Quote:

Originally Posted by bridge8989 

the weird thing is that under task manager i dont see any particular program taking up much memory (doesnt add up to 85% of 2gb ram).  Even exiting foobar/everything doesnt free up ram; i have to reboot.

Interesting.  Was that with the box 'show processes from all users' checked?  audiodg.exe might be hidden there.  I have no problems whatsoever on my netbook with a mere 1gb of RAM.  (Win7-32, though.)  I'm thinking that it's a routing problem, or driver error.  Was that to your onboard SPDIF output?

Quote:

Originally Posted by bridge8989 

the only user account is mine but ill double check when im home.  ive tried using both spdif and usb.  Ill probably try reformatting if it doesnt get fixed.

The way Windows works is it creates virtual users, and runs processes from them.  audiodg runs from the LOCAL SERVICE identifier.

Quote:

Originally Posted by bridge8989 

 

the weird thing is that under task manager i dont see any particular program taking up much memory (doesnt add up to 85% of 2gb ram).  Even exiting foobar/everything doesnt free up ram; i have to reboot.

It is best to run at least 4gb on Win7 64.

I do and have never had any problems with fobar/wasapi even with a myriad of other programs running.

Quote:

Originally Posted by bridge8989 

yea ive had 4gb in my computer but my mobo is crappy and cant support 4dim's without overvolting.  But overvolting made my computer crash randomly while play starcraft 2 so I currently have 3gb running stable without overvolting right now.  Ram still went to 80-90% without anything running except foobar.  So i tried 2gb again and still ran into the same problem problem.

 

so far ive been using asio4all and it seems to be working fine.  i might just downgrade back to 32bit cuz 64bit has been causing quite a few problems for some applications.

i have the same.. win 7 64 bit, foobar, wasapi...blah blah... i also used to be a IT manager, so ill do my best to help if youre interested

first of all the red flag went up as soon as i saw the word "recently" 

does this "memory leak" only happen when you are using foobar?

are you running any other DSP's or VST's?

are you having any other issues with your computer whatsoever, no matter how mundane or seemingly unrelated?

just as a precaution i would download and run a few spyware removal tools.. especially since the issue isnt showing itself in your task manager

spybot search and destroy is free and excellent

another thing you might try if you're comfortable/able is reach in your computer and make sure the ram is seated fully and that your computer is clean.

also very important, if you can think of ANYTHING that may have changed on your computer about the time this started happening, that would be helpful

download this program - process explorer - it is much more thorough in outlining what is using what on your computer.. you can post a screen shot of that program running while you are having your memory leak and that would probably help too.

also make sure you have the latest drivers for your realtek integrated sound module

keep us posted...

I recently started using Wasapi on my Win7x64 foobar 8gb ram.  I notice problems if the usb device isn't hooked in good,  probably due to a cheap USB cable. 

Foobar shouldn't take more than a few % of CPU power (provided you don't use DSPs, plugins extensively), or more than 100 MB memory (that's with a really big library, without the library management, no more than 10 MB).

Otherwise it may be a virus.

Foobar has a memory leak, and it's usually something to do with an outdated or bad user-installed component.

See if the problem goes away if you remove/update components.

I've had foobar hit a few hundred mb of memory usage in the past. Cleaned out components, now it doesn't use over 25mb (well, it uses more during play since it's set to fully buffer files, but that's another story...)