{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
5/9/2019 4:08:20 AM
6
-
Windows 7 Ultimate. 64 bit. I have done literally everything related to drivers. I have done the power cycling. Starting game up before anything else after a restart. Update drivers. Rollback drivers. Uninstall and reinstall. I have done it all. Unless you are going to tell me Destiny 2 stopped Windows 7 support?
-
Few search results for the memory leak issue: [url=https://answers.microsoft.com/en-us/windows/forum/windows_7-performance/audiodgexe-uses-extreme-amounts-of-memory-and-is/d2202857-0a63-4aa4-a278-2e97e6377bee?messageId=fc62f2ec-c0e6-417a-b71a-7810862818b5&page=2]ref1[/url] [url=https://appuals.com/fix-high-cpu-usage-audiodg-exe/]re2[/url] [url=https://www.drivereasy.com/knowledge/fix-windows-audio-device-graph-isolation-high-cpu-usage-issue/]ref3[/url] [quote]Unless you are going to tell me Destiny 2 stopped Windows 7 support?[/quote] While this is not the case, it should be noted that Windows 7 is nearing its EOL (End of Life) in January 2020 ([url=https://www.microsoft.com/en-us/windowsforbusiness/end-of-windows-7-support?SilentAuth=1&wa=wsignin1.0]source[/url]). It is recommended to upgrade to Windows 10 (in most cases you can use the Win7 key to activate the upgrade).
-
That is literally not a good reason for this to be happening. Not only has it NOT reached EOL yet, but that shouldn't cause Destiny 2 to leak memory in audiodg.exe :\ You have no idea what's wrong. Those links I have ALREADY checked. The fact is, Destiny 2 has had a memory leak issue since launch for hundreds of users and there hasn't been a fix for it. This ONLY occurred with the recent update. ONLY with the recent update. ONLY the recent update. ONLY after I updated to the most recent update. ONLY after the update.
-
I didn't even imply it was because the pending EOL of Windows 7. I merely provided additional notes based on your question regarding Windows 7 support. As a Windows 7 user myself, I have not experienced this issue, nor do I recall seeing posts about it before this one. Also, I provided links to issues with same/similar signature, and based on what was or wasn't explicitly mentioned in the thread. Could you share a link showing that this memory leak or any that shares at least similar characteristics affecting hundreds of users? Any links provided could prove useful in any investigation into the issue.
-
Edited by Miki the Dragon: 5/10/2019 5:54:00 PMhttps://www.reddit.com/r/DestinyTechSupport/comments/a168vj/memory_leak_issue/ https://www.reddit.com/r/DestinyTheGame/comments/bd4vuy/any_fix_for_the_memory_leak_problem/ https://www.reddit.com/r/DestinyTheGame/comments/a7iv7k/memory_leaks/ (this one lines up with my timeframe) https://www.reddit.com/r/DestinyTechSupport/comments/9kemw4/persistent_memory_issues_even_after_closing/ https://www.reddit.com/r/DestinyTheGame/comments/7z00r9/memory_leak_on_pc_is_still_a_big_issue/ https://www.reddit.com/r/destiny2/comments/a4qwfp/pc_memory_leak_severe_lag/ https://www.reddit.com/r/DestinyTechSupport/comments/79mh31/memory_leak_pc/ https://www.reddit.com/r/DestinyTechSupport/comments/79jgjz/official_memory_leakfps_drop_thread/ https://www.reddit.com/r/DestinyTechSupport/comments/79y3po/memory_leak_problem_i_think/ https://www.bungie.net/en/Forums/Post/242734439 https://www.bungie.net/en/Forums/Post/238679995 https://www.bungie.net/en/Forums/Post/237072305 It was apparently fixed in either 2018 or 2017 in a hotfix, but it still affects people. Not to as large a degree as back then, but is still there. Especially with the Revelry and after the Revelry. I've done 100% fine until that update. I have done ALL troubleshooting available. ALL of them. And before you ask "well, it's impossible for anyone to do all of them" I've had this problem for awhile now. Uninstalled drivers. Reinstalled. Updated. Power cycled. Run as admin. Used different audio devices. Different driver versions. I've done it all.
-
[quote]It was apparently fixed in either 2018 or 2017 in a hotfix, but it still affects people. Not to as large a degree as back then, but is still there.[/quote] Yes, the memory leak(s) were fixed in earlier patches, and may or may not be related to the issue you are facing. Most of the links do not contain actual logs/images of leak, so hard to say what the cause in each case might be. Also, some of them are old and not necessarily applicable anymore (lack of update either way in thread). Some threads even state the fix is already in (back then). One theme that does stand out, is you do mention having this issue for quite some time, but on the other hand that it started happening after the most recent update (or the one before). Thus, the actual start time of this issue is currently uncertain. Lastly, I would just like to note that I was only trying to help you based on information available in this thread. Hope you find a fix. Best of luck.
