Mupen64Plus-Core
Mupen64Plus-Core copied to clipboard
OpenEmu
OpenEmuHelper Process
Sometimes after I quit OpenEmu, the OpenEmuHelper process keeps running in the background maxing out the CPU. This has happened at least 2-3 times over the last few weeks.
Steps to reproduce
- Launch OpenEmu and play for a while
- Quit the app (cmd Q is how I close everything)
- Wait to see if process sticks around… (it doesn't happen consistently)
Note: I usually play at night and notice this slowdown the next morning when working. Killing the process in Activity Monitor fixes the issue.
Observed Behavior
Here's a screenshot of the process (OpenEmu is not open).
Debugging Information
- OpenEmu Version 2.0.7
- macOS High Sierra 10.13.6
- MacBook Pro (13-inch, 2017, Four Thunderbolt 3 Ports)
I hope this helps. Please reach out if you need any additional info. I love the app and really appreciate all the hard work you all put into it!
Contributing guidelines - "Be as detailed and specific as possible..." and "Include Console and crash logs, macOS and OpenEmu version, hardware information, ROM/game filenames, etc."
That likely means a core plugin crash. What game and system?
Sorry about that, I tried to be as specific as possible. The OpenEmu version and hardware information is in my original post (see the bottom of it).
That said, I didn't think to include the system / last game I was playing. The system was N64 and I think the last game was Pokemon Snap. Again, OpenEmu didn't crash, it was working great. It wasn't until the morning after playing and quitting OpenEmu that I noticed this rogue process pegging my CPU.
Let me know if you need anything else. I really appreciate the help.
I changed OpenEmu's emulation to run in a background thread and... well, I noticed something that might be related while playing Paper Mario: Master Quest.
Even when the emulation is paused, the emulator uses 200%+ of CPU while the game is loaded!
Development statistics: • macOS 10.12.6 (Sierra) • OpenEmu 2.0.9.1:058-g8850505, running the Mupen core of course • Late 2014 (Retina) MacBook Pro with i7-4980HQ CPU @ 2.80GHz • 16 GB RAM • NVidia GeForce GT 750M with 2 GB.
@bkimmett You are not meant to use "background thread" for running games. That is a mode used for debugging cores within Xcode.
The thing is, I did it to check that the emulation thread was the problem, and it appears that's the case. After further testing with 'Background Thread', even after I stopped the emulation, OpenEmu continued to use 200% of the CPU until it was quit - the same behavior that was previously observed in the Helper Tool process.