+- Dolphin, the GameCube and Wii emulator - Forums (https://forums.dolphin-emu.org)
+-- Forum: Dolphin Emulator Discussion and Support (https://forums.dolphin-emu.org/Forum-dolphin-emulator-discussion-and-support)
+--- Forum: Support (https://forums.dolphin-emu.org/Forum-support)
+--- Thread: [SOLVED] Memory leaks with latest development builds (since 4.0-298) (/Thread-solved-memory-leaks-with-latest-development-builds-since-4-0-298)
[SOLVED] Memory leaks with latest development builds (since 4.0-298) - Knuckles500 - 11-18-2013
Hey everyone.
I noticed that ever since 4.0-298, Dolphin causes massive memory leaks as soon as I either load a game or when I click the GCPad and Wiimote config icons (every other part of the GUI works perfectly normal). When I either run the game or try to open the GCPAD/Wiimote config, the game never loads and the config windows never appear. Memory consumption of Dolphin increases which causes my other programs to crash or hang until I end the Dolphin process. Sometimes I can usually get an APPCRASH out of Dolphin, but it seems to be a bit random. I noticed when it does crash, one of the modules that's affected is msvcr120.dll. I take it you guys are moving to Visual Studio 2013?
Dolphin 4.0.1 and 4.0-291 work fine, any revision that was compiled either by the build bot or someone else causes these issues for me. x64 and x86 both cause the issues for me as well. Normally I'd open an issue on the tracker for this, but I suppose since there hasn't been any complaints about it then it's definitely all on my end.
Here's what I've done to try and fix my problem.
1.) Install VC++ 2013 Redist x86 (I noticed that Dolphin began including the dll prerequisites sometime after 4.0-298 but I decided to install the redist myself just in case)
2.) Reinstalled other versions of the VC++ Redistribution, no change
3.) Removed the 'Dolphin Emulator' folder from Documents, no change
4.) Uninstalled MotionJoy, I know it was a dumb idea to have this is in the first place, but I thought maybe there was a problem with the crappy drivers (which could have explained why it was crashing the controller configs) but no change either
Currently the problem persists for me as of 4.0-399 x64. I'm thinking it might be a problem with what I have for controller drivers or something related. I heard that MotionJoy was a pain in the ass to get rid of even after uninstalling it, so maybe a remnant is conflicting? I really have no idea at the moment. I do believe it is related to VC++ 2013 though. I know this branch is unsupported, but the 'dx9-final' branch also causes the same issues for me but the build that Tino provided is based on 4.0-140 but was compiled with Visual Studio 2013.
My specs:
Windows 7 Home Premium x64
Intel 2500k 3.4 ghz
NVIDIA GeForce 680 GTX (331.65)
Crucial 8GB DDR3 (I don't remember the specific model at the moment, sorry)
If you need more information please ask. Dolphin doesn't seem to generate any error logs when this problem occurs. I'm in the process of trying to get the Windows error message when this occurs so that it can give a clearer picture of the problem, but I had to post this first just in case it causes my web browser to crash. I'll edit this post with the information as soon as I can.
EDIT: Here's something. Sometimes when the memory consumption increases by a lot when I try and open the GCPad/Wiimote config the consumption will go down and a "An unhandled exception occurred" message appears. Then after that I get a "*** Caught unhandled unknown exception; terminating" message. Then "Dolphin.exe has stopped working", which gives me a few variants:
Quote:Problem signature:
Problem Event Name: BEX64
Application Name: Dolphin.exe
Application Version: 0.0.0.0
Application Timestamp: 52819a58
Fault Module Name: StackHash_49d6
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 00000000
Exception Offset: 000000000000004d
Exception Code: c0000005
Exception Data: 0000000000000008
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
Additional Information 1: 49d6
Additional Information 2: 49d6e5125bb7a4bb3f0b5f78de512c57
Additional Information 3: 83f3
Additional Information 4: 83f33ee37c99e11b47e4d95ee823e2cb
Quote:Problem signature:
Problem Event Name: APPCRASH
Application Name: Dolphin.exe
Application Version: 0.0.0.0
Application Timestamp: 52819a58
Fault Module Name: Dolphin.exe
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 52819a58
Exception Code: c0000005
Exception Offset: 000000000043996e
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
Additional Information 1: 7206
Additional Information 2: 72061b2c65c39dd657ffb9703817dd67
Additional Information 3: c717
Additional Information 4: c71705ecd65e41a828530c68daaa7c61
I recall a similar error but with the msvcr120 module. Unfortunately, this is from the "dx9-final" compile and not from 4.0-399. I managed to produce similar errors with 4.0-399 by letting the process run when memory consumption peaked and started to come down.
RE: Memory leaks with latest development builds (since 4.0-298) - neobrain - 11-18-2013
4.0-xxx build numbers are useless, please post the git hash (gibberish) from the about dialog in Dolphin.
RE: Memory leaks with latest development builds (since 4.0-298) - Knuckles500 - 11-18-2013
Sure thing:
4.0-140 (dx9-final) - bcd5b857a9a126242dde50144eba9194886f2e6f
4.0-291 (master) - 498d4919427dae147917b65cfc96f7c6af48e12c
4.0-298 (master) - e22ff4927ae53a116edd72664f7fdc2a8cd9b958
4.0-399 (master) - e805bf60685bb5f4bd5ac1bf0a290519a678e5b4
RE: Memory leaks with latest development builds (since 4.0-298) - Knuckles500 - 11-25-2013
I apologize for double posting in the thread, but here's something else I neglected to mention.
Every time Dolphin crashes when trying to open the GC/Wii Pad Config, Dolphin generates some information in exceptioninfo.txt. It doesn't seem to output information to any other log file (like dolphin.log). Here's what happened when I tried to open the GCPad config:
Quote:Unhandled Exception
Code: 0xC0000005
Call stack info:
0x00000000 : ?
Dolphin!0x00582667 : ?
Unhandled Exception
Code: 0xC0000005
Call stack info:
0xEF43CCEB : ?
0xFFFFFFFE : ?
0xFE000007 : ?
0xFFFFFFFF : ?
Dolphin!0x00FFFFFF : NvOptimusEnablement
When I tried to open the Wiimote config I got a very similar error as the one mentioned before.
I noticed that I was getting APPCRASH errors with MSVCR120 only when I tried to run a game. Dolphin will display a black screen when executing the game but never display the frame rate or other onscreen information on launch (it displays the path of the game image in the bar below but that's as far as it goes). Here's the report for when that happens in case you needed to see it:
Quote:Problem signature:
Problem Event Name: APPCRASH
Application Name: Dolphin.exe
Application Version: 0.0.0.0
Application Timestamp: 5291f1d9
Fault Module Name: MSVCR120.dll
Fault Module Version: 12.0.21005.1
Fault Module Timestamp: 524f83ff
Exception Code: 40000015
Exception Offset: 0000000000074a46
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
Additional Information 1: 24a5
Additional Information 2: 24a57eb8df7225c8a7590103b987ac86
Additional Information 3: 121e
Additional Information 4: 121e5adfca9ce6a98c53e7e397a45ade
Just to see what would happen I removed MSVCP120, MSVCR120, and VCOMP120 from the Dolphin directory to see if the same problem occurred again and it did (no variation as far as I can tell). However, I understand that perhaps when I installed the VC++ 2013 Redist that it probably installed it's own copies of the modules somewhere in the Windows directory.
I doubt any of this helps but I thought it was worth mentioning. This was all gathered using a different version of Dolphin (Dolphin 4.0-426 12741f6406899f7e184cd2139c83e215c43a90f8). I'm starting to wonder if I'm missing some kind of dependency.
RE: Memory leaks with latest development builds (since 4.0-298) - Knuckles500 - 05-19-2014
I apologize for the triple post and bump, but I wanted to give this a follow up just in case others were having issues too.
I eventually identified and fixed the problem. It seems that my game controller (a dualshock3) had a duplicate entry under the Device Manager. The duplicate entry was still using an older version of the driver. So I just disabled the older one and Dolphin worked as expected. Older revisions seemed to work fine with the duplicate entry enabled, so I never suspected it.
Not sure if this would be considered a user error then. If you'd like more information (perhaps on the drivers that are being used) feel free to ask. If not, feel free to ignore.
RE: Memory leaks with latest development builds (since 4.0-298) - KHg8m3r - 05-19-2014
Is there any reason that you haven't upgraded your GTX 680 drivers?
RE: Memory leaks with latest development builds (since 4.0-298) - Knuckles500 - 05-19-2014
Uh, because this is an old thread? Of course I've updated my drivers since then. I'm using 337.50. I've recently updated Dolphin to 4.0-1601 (6950f533aee33cbdce7ecfd5f59e3aba3836e730). Not sure why that's relevant, either.
RE: [SOLVED] Memory leaks with latest development builds (since 4.0-298) - KHg8m3r - 05-20-2014
You did ask yesterday if there were any other questions about drivers
