Everytime a new audio file is played (foobar200, mpc-hc) or youtube video (basically anything that plays audio), the Audiodg.exe process grows in about 5-10MB chunks each time a new audio source is played. I can reproduce this by stopping and playing any audio file repeatedly in any media player.
I discovered this leak just recently when I had not restarted my computer in a week of 24/7 usage and got a Windows out of memory warning and noticed audiodg.exe was using about 2.5GB of memory.
I'm using onboard sound which is an ALC898 Realtek chip with the latest Realtek drivers. Tested with Equalizer APO v.1.0 and v0.9.2. Tested on Windows 10 and 7. Leak occurs on both versions of Equalizer APO and Windows. Even with an empty config.txt file it still happens.
It's kinda inconvenient having to tweak the registry to fix this. Is this bug gonna be fixed in the forseeable future? Is there some audio setting I should have enabled/disabled before installing Equalizer APO?
Last edit: Vanquo 2015-11-02
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I just checked and you are right, the APO supplied by the sound card driver ("original" APO) is not released when E-APO is shutting down, which will likely be the cause of your memory leak. This problem must have been there from the beginning. I guess I didn't notice it because the amount of leaked memory is not much with my sound card driver. The memory consumption only rised by a few kilobytes each time. I have added the missing code and it will be part of the next release.
It's kinda inconvenient having to tweak the registry to fix this
You no longer need to manipulate the registry to disable the original APO. The Configurator now contains "troubleshooting options", which allow you to disable the original APO for the pre- and post-mix stage. So, until this bug is fixed, my advice is that you try to undo your manual changes to the registry and use the Configurator to disable the original APO. That way the registry values will be automatically restored if you should uninstall E-APO.
Anyway, thank you for reporting this and for the amount of time you invested to find the cause of this problem.
Last edit: Jonas Dahlinger 2015-11-02
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Everytime a new audio file is played (foobar200, mpc-hc) or youtube video (basically anything that plays audio), the Audiodg.exe process grows in about 5-10MB chunks each time a new audio source is played. I can reproduce this by stopping and playing any audio file repeatedly in any media player.
I discovered this leak just recently when I had not restarted my computer in a week of 24/7 usage and got a Windows out of memory warning and noticed audiodg.exe was using about 2.5GB of memory.
I'm using onboard sound which is an ALC898 Realtek chip with the latest Realtek drivers. Tested with Equalizer APO v.1.0 and v0.9.2. Tested on Windows 10 and 7. Leak occurs on both versions of Equalizer APO and Windows. Even with an empty config.txt file it still happens.
I searched and found this thread with a similar issue https://sourceforge.net/p/equalizerapo/discussion/general/thread/0b82e472/ But I'm not sure if it applies to me since im using just basic onboard sound.
update:
Well I just tried tried the workaround from this post https://sourceforge.net/p/equalizerapo/discussion/general/thread/0b82e472/#9543 and what do you know... it works. No more memory leak. I also noticed a new option called "Enable audio enhancements" in the advanced tab of the speaker properties.
It's kinda inconvenient having to tweak the registry to fix this. Is this bug gonna be fixed in the forseeable future? Is there some audio setting I should have enabled/disabled before installing Equalizer APO?
Last edit: Vanquo 2015-11-02
I just checked and you are right, the APO supplied by the sound card driver ("original" APO) is not released when E-APO is shutting down, which will likely be the cause of your memory leak. This problem must have been there from the beginning. I guess I didn't notice it because the amount of leaked memory is not much with my sound card driver. The memory consumption only rised by a few kilobytes each time. I have added the missing code and it will be part of the next release.
You no longer need to manipulate the registry to disable the original APO. The Configurator now contains "troubleshooting options", which allow you to disable the original APO for the pre- and post-mix stage. So, until this bug is fixed, my advice is that you try to undo your manual changes to the registry and use the Configurator to disable the original APO. That way the registry values will be automatically restored if you should uninstall E-APO.
Anyway, thank you for reporting this and for the amount of time you invested to find the cause of this problem.
Last edit: Jonas Dahlinger 2015-11-02
Ah troubleshooting options, so that's what it's for :D That's easy enough. Thanks for the tip. Keep up the good work!