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 in audiodg.exe (Read 4102 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Memory leak in audiodg.exe

foobar2000 v1.3.1 causes a memory leak in the Windows Audio Device Graph Isolation (audioadg.exe) while a song is playing if the song is stopped and restarted.  This was found my watching the memory footprint in Task Manager for the audioadg.exe image.  While the song is playing the memory usage will be relatively constant and when the song is stopped the memory usage of audioadg.exe will go down.  When the song is started the memory usage will be higher than the last time the song was playing.  Repeated stopping and starting will continue to cause audioadg.exe to increase its memory footprint over time when actively playing a song.  Typical start and stop timing was 1-3 seconds between button pushes.  The memory increased by 0.5-0.7MB per stop/start combination.

The same testing was completed using Windows Media player and the problem did not occur.

The following is system configuration information:
Lenovo Y510P notebook
Realtek audio
16G memory
Windows 8.1 fully updated
Foobar2000 v1.3.1 (and previous) with no plug-ins
audioadg.exe v6.3.9600.16384 vendor Microsoft

 

Memory leak in audiodg.exe

Reply #1
What was the final, maximum memory use by audiodg? Have it crashed? I don't think it's a memory leak, just lazy windows memory management. If I would be so scared about every 0,5MB memory increase I would spend my life writing on various forums and requesting patches...

Memory leak in audiodg.exe

Reply #2
foobar2000.exe is causing audioadg.exe to use continually more memory with no final limit in sight.  foobar2000.exe has crashed or had odd behavior especially after a suspend.  Closing foobar2000.exe does not correct the memory leak that it initiates in audioadg.exe unless audioadg.exe also closes.

I find it interesting that a memory leak is so easily dismissed, even if the amount of memory is small, given the number of problems it can cause.  Please note that other programs that use audioadg.exe do not cause the same problem including Windows Media Player and Chrome.

Just reporting a bugreport, fix or don't fix.

Memory leak in audiodg.exe

Reply #3
OK, so it seems we have serious crash. It could be nice if you could submit your crash report using upload section and link it here, for devs look. Additionally you should provide ALL relevant details - like used output method, used output device (which exactly realtek do you use), windows version, drivers for soundcard version, foobar version, list of plugins used, how to reproduce bug,  etc - everything is explained in sticky post in the beginning of "Support" subforum. Currently you provided only partial information on system specs and problem details. If you don't follow steps contained there, then don't expect serious attention and quick bugfix.
Anyway - you seem to be the only one who have such problem.