T
Travis King
audiodg.exe was eating 300MB of RAM here on Vista RC1 tonight. Anyone else
have problems with this?
have problems with this?
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
G
Guest
Yeah, you've stumbled upon a bit of a toughie there...
I assume that, as you're running Release Candidate 1, you were also running
Beta 2?
This issue seems very limited, and I was hoping that it would have been
addressed in RC1 (I've yet to install. Everytime I try to download it comes
up as 907 bytes...). If you'd like some more details regarding it, check
back, there is a post started by ThrmanMunson15, titled audiodg.exe. While
his problem differed from yours (and mine), all responses seemed to be more
like yours. Hell, if audiodg.exe was eating just 300 MB of RAM... I've seen
it peak at about 1.73 GB, which is impressive, considering DWM and one of the
service host take up about 200 MB alone. Ending the process will gain me back
1.6 GB of ram and nearly 3 GB of pagefile, typically. Right now it's sitting
on about 375 MB, which is not really that big a deal at the moment.
As for details, I'd like to follow this up further, and see what can be
seen. Would you happen to be running a Creative sound card? I've seen no bias
as to x64 of x86 as of yet, but there seems to be a correlation between
Creative sound cards and this audiodg.exe memory leak. Perhaps we should
actually document some _useful_ information regarding this, and see if we can
get an MVP to stop by this post. Honestly, it's annoying having to kill my
sound. Some people can't even do that, such as ThrmanMunson15.
I assume that, as you're running Release Candidate 1, you were also running
Beta 2?
This issue seems very limited, and I was hoping that it would have been
addressed in RC1 (I've yet to install. Everytime I try to download it comes
up as 907 bytes...). If you'd like some more details regarding it, check
back, there is a post started by ThrmanMunson15, titled audiodg.exe. While
his problem differed from yours (and mine), all responses seemed to be more
like yours. Hell, if audiodg.exe was eating just 300 MB of RAM... I've seen
it peak at about 1.73 GB, which is impressive, considering DWM and one of the
service host take up about 200 MB alone. Ending the process will gain me back
1.6 GB of ram and nearly 3 GB of pagefile, typically. Right now it's sitting
on about 375 MB, which is not really that big a deal at the moment.
As for details, I'd like to follow this up further, and see what can be
seen. Would you happen to be running a Creative sound card? I've seen no bias
as to x64 of x86 as of yet, but there seems to be a correlation between
Creative sound cards and this audiodg.exe memory leak. Perhaps we should
actually document some _useful_ information regarding this, and see if we can
get an MVP to stop by this post. Honestly, it's annoying having to kill my
sound. Some people can't even do that, such as ThrmanMunson15.
G
Guest
I have been having the same problem as well. But it was certainly not as bad
as your audiodg; mine 'only' took 200-300MB of ram (the problem is I only
have 512MB of ram).
I am using RC1 x86, and this problem occurred since I installed RC1 (clean
install, no upgrade from beta 2). I have also used beta 2, but I didn't have
the problem there.
I am not using Creative Soundcard, but the Realtek High Definition Audio. So
it seems the problem occurs with those kind of soundcards as well.
Are there still no solutions to this problem?
Floris
as your audiodg; mine 'only' took 200-300MB of ram (the problem is I only
have 512MB of ram).
I am using RC1 x86, and this problem occurred since I installed RC1 (clean
install, no upgrade from beta 2). I have also used beta 2, but I didn't have
the problem there.
I am not using Creative Soundcard, but the Realtek High Definition Audio. So
it seems the problem occurs with those kind of soundcards as well.
Are there still no solutions to this problem?
Floris
G
Guest
I have been having the same problem here. audiodg.exe is chewing up about
600MB of memory (have 1GB total). I have an Audigy 2 ZS card using the
latest beta drivers from Creative. I didn't have this problem in Beta 2, but
now it gets to the point where my system reverts to Aero Standard because it
doesn't have enough memory to run Glass. I don't know if this is a memory
leak or just a major bug, but no single Windows program should take up 60% of
my total resources.
600MB of memory (have 1GB total). I have an Audigy 2 ZS card using the
latest beta drivers from Creative. I didn't have this problem in Beta 2, but
now it gets to the point where my system reverts to Aero Standard because it
doesn't have enough memory to run Glass. I don't know if this is a memory
leak or just a major bug, but no single Windows program should take up 60% of
my total resources.