Emulator

Ok let me just try to clarify this - anything older than 4.0-9507? So on builds after 4.0-9507, such as all 5.0 era builds, it doesn't occur?

MayImilae wrote:

Ok let me just try to clarify this - anything older than 4.0-9507? So on builds after 4.0-9507, such as all 5.0 era builds, it doesn't occur?

No anything newer than 4.0-9507

MayImilae wrote:

Ok let me just try to clarify this - anything older than 4.0-9507? So on builds after 4.0-9507, such as all 5.0 era builds, it doesn't occur?

I meant to say newer ... can an admin please fix that XD

Hey so I have a video ready but its not finished going through publishing anyways here is the link https://youtu.be/znjylaFNTwA
When its available admins can see first hand the weirdest bug I have ever seen.

P3rf3ct_Zer0 wrote:

Hey so I have a video ready but its not finished going through publishing anyways here is the link https://youtu.be/znjylaFNTwA
When its available admins can see first hand the weirdest bug I have ever seen.

Turn your pc up loud my mic is aweful

It looks like there's an object handle leak of some sort. The handle count is increasing steadily throughout the video, and as soon as Dolphin's closed the count drops by over 20,000.

Here is some stuff you can do to narrow it down: https://blogs.msdn.microsoft.com/dsui_team/2013/04/23/debugging-a-gdi-resource-leak/ (start at the part with task manager).

In case it is the cause or related: I can reproduce the permanently increasing handles here, too. I never experienced increasing CPU usage after extended play, though.

(It might still be caused by the open handles for OP if, let's say, he has some particular HID hardware connected that I don't have and which does processing for each open handle to its device or if he has some kind of tool installed that hooks into the controller communication (let's say Xpadder or similar) and that also does processing per open handle.)

If I switch off "Continuous Scanning", the number of handles allocated by Dolphin remains constant.

@P3rf3ct_Zer0 can you try with Continuous Scanning disabled? (You can click "Refresh" in the controls window during the game if it didn't detect the Wiimotes connected to the Mayflash DolphinBar at startup in that case.) Does the CPU usage issue still happen for you without Continuous Scanning?

Thanks for the hint, i can repro the handle leak with continuous scanning enabled, too. Note that it seems the performance problem occurs on the video around 0xffff handles in the dolphin process..:)

should fix it: https://github.com/dolphin-emu/dolphin/pull/5626

JosJuice wrote:

https://dolphin-emu.org/download/dev/13b1fa2c658c2c0fd841449b54e4509f757cdcbc/

Thank you I can confirm this fixes the issue.