Emulator

I would like to change that it starts at 298! NOT 299.

https://forums.dolphin-emu.org/Thread-extreme-memory-leak-with-version-4-0?pid=315091

I think it will require a proper dump of the process at the time of the leak in order to debug, which might be challenging to obtain unless you're familiar with windows debugging.

helpful links:
http://www.iis.net/learn/troubleshoot/performance-issues/troubleshooting-native-memory-leak-in-an-iis-7x-application-pool
http://www.codeproject.com/Articles/31382/Memory-Leak-Detection-Using-Windbg

we can set it up such that I debug your dolphin.exe remotely:
http://www.nynaeve.net/?p=32

So, to create a good dump for this:
(This assumes you have gflags (part of debugging tools for windows), and your dolphin binary is called dolphin.exe)

• open cmd as admin press windows key, type "cmd", press ctrl+shift+enter, press alt+y
• enable usermode stack trace: "c:\Program Files (x86)\Windows Kits\8.1\Debuggers\x86\gflags.exe" /i dolphin.exe +ust
• run dolphin and trigger the leak
• create a dump open task manager, right click on dolphin and "create dump file"

• The dump should be in %localappdata%\Temp\, upload it or send it to me somehow

• turn off UST when done!
  "c:\Program Files (x86)\Windows Kits\8.1\Debuggers\x86\gflags.exe" /i dolphin.exe -ust

ok...this is only reproducible on debug builds of dolphin for me.
http://pastie.org/private/7ag97xqq1ulzhggfpj79w
http://pastie.org/8907015

forcing _ITERATOR_DEBUG_LEVEL undefined for xstring file fixes some of the leaks...

Hey godisgoverment, I'm not so good at debugging programs, I'm more of a hardware kind of guy. But anyways, You said above that you were able to reproduce the problem, does this mean you found the issue? If you need any of my help, let me know.

I would also like let you know that it isn't just GCPad, it's also the wiimote menu, AND when I try to start up the game.

Mike, how were you running Dolphin exactly?

Was it a debug build? Were you using visual studio?

Was it just a plain release build ?

It is just the plain release build. I could download visual studio, if need be, and run it through that.

Nope that's ok, it's just weird as we could only reproduce it in debug. :\

I just feel like I'm missing a files or something, since I am using a near fresh install of 8.1. I don't have everything that I normally have on my computer.. But I can't think of anything else that would be missing..

Any update on a fix?

This commit https://github.com/dolphin-emu/dolphin/pull/352 will fix memory leaks - but only in debug build. If you weren't experiencing the issue in a debug build, it won't help.

Hey there. I just noticed this issue report now, but it seems that we both have the same exact issue going on. Have you looked at this thread?

https://forums.dolphin-emu.org/Thread-solved-memory-leaks-with-latest-development-builds-since-4-0-298

For me, the problem was that I had a duplicate entry for a game controller under Device Manager. One entry was using an older version of the driver than the other. Previous versions of Dolphin never had a problem with this, it was only until the VS2013 changes that it became a problem. And as you said, I encountered the same issues at the same exact spots (GCPad, Wiimote, and game start up).

I fixed it by disabling the entry of the my game controller under device manager that was using the old driver. After that, everything worked as expected.

I hope this also applies to you.

Hey everyone, super late reply. I just tried the last two fixes up above^ and none of them seemed to work. I'd really like to use a stable version so I can play smash with my buddies, but I've been using 3.5.

More updated information, I at first thought it had to do with my being on Windows 8.1, but earlier today I installed Windows 7, and it still didn't work. I have a feeling it's hardware compatibility, here's the list: http://prntscr.com/3yjj1h

Any further questions, please ask.

@knuckles, WOW THANK YOU SO MUCH THIS REALLY FIXED IT! I just got onto my 8.1 partition and did exactly what you said, and it FUCKING WORKED! I am so thankful right now, really thank you so much!