BUG - Hanging Process

[darkness93]

Hey guys,

so after I've had some awesome fun with Dolphin, I stop emulation through the Stop button on the main window and all's good here. However, sometimes I'll close the main window using the normal "X" on the top right or right clicking the icon on the taskbar and clicking "Close window". This leaves a process running in Windows Explorer which starts to freeze up my computer somehow, and when I try to kill it (I've used task manager, powershell, Process explorer and tried to find a Service and stop it) it says Access Denied. When I go into properties it seems to think it's associated with the "C:\Windows\Windows32" path so that's very strange..

The weird thing is that if from the main Dolphin window I were to click File > Exit instead then there is no hanging process and everything seems normal. The only way I've been able to fix the hanging process is to restart my computer which takes ages with all the stuff I've got installed :p

Would be great if this could be looked into, it doesn't happen with the other emulators I use.

Cheers,
Daniel 

[envisaged0ne]

You stated that you're using 4.0 in your profile. That version is no longer supported, so you need to update to either 5.0 or one of the latest Dev builds. Make sure you're downloading Dolphin from the official website. Also make sure you're not running it from your Program Files, or Program Files (x86) folders

[darkness93]

Sorry I haven't updated that, I've been using 5.0 recent decades for a while now. Currently I'm on 5.0-3489 so yep due for a Dev build download again but I don't know if it'll fix the problem and I don't entirely want to test it with the freezing​ up of my computer it causes.. will keep you updated though and I can try tonight before I go to bed. Emulator itself is running very smoothly btw, had a great game of Mario Kart with my friend last night

[darkness93]

Out of habit I closed Dolphin from the taskbar today, but nothing seems to hang and all seems good! May have been that specific Dev version, I got the now-latest today which was 5.0-4337

[ImpulseOS]

Im using the latest dev build and noticed that in windows explorer multiple instances of dolphin were running and just like above i could not close them although there was no error or lock to say i could not, it was like the end task button would not work for any of the dolphin processes (could close other things though). They ended up using all my RAM and my computer locked up. I think it was when i was running directx 11 and the game would not show up so i quit emulation and it looked like it worked but it seems to have just stayed on the processes.

[envisaged0ne]

ImpulseOS, you are reporting a completely different issue. Please create your own thread. Otherwise your hijacking someone elses thread & that's frowned on

[shuffle2]

darkness93 if you see it happen again please try to narrow down if it's tied to specific settings such as graphics/audio backends in use.

[ImpulseOS]

(06-16-2017, 08:28 AM)envisaged0ne Wrote: ImpulseOS, you are reporting a completely different issue.  Please create your own thread.  Otherwise your hijacking someone elses thread & that's frowned on

Doesn't sound different to me, he reported multiple instances where he closes down the program and it stays on his Task manager, the only difference being he was using a different version of dolphin. I cant see how 'hijacking' this would be frowned upon, by who? I have a similar issue so its not like the thread owner would be mad at me... 

[envisaged0ne]

You're not getting an error. It's sucking up all your RAM. It's probable that it's caused by a different issue than what the OP was having. Unless you have the EXACT same problem where we can give you both the exact same advice. Or your are offering help to the OP, it's hijacking. I have a hunch what the problem is..so post a new thread

[darkness93]

Hey cut him some slack, it does actually sound like the problem. I too had a moment where there were multiple processes, though in both our scenarios it seems we're unable to stop the "emulation" that the program still thinks it's doing. I haven't managed to recreate the problem yet, all seems good since I moved to the later dev and will try to get back in the habit of always downloading the latest dev. It seems to shut down gracefully if I close it with the top right "X" or from the taskbar. I will let you guys know as soon as it happens again and what I think caused it, but to this day I have no idea really!