MO still resident after close

[enkephalin07]

I don't know how to reproduce it, but I've twice seen ModOrganizer.exe listed as a process after closing. No disk activity, it just occupies RAM and an unjustifiable amount of CPU%. Opening MO again creates a second process that consumes RAM and CPU appropriate for the tasks it's performing. Killing either process tree does not affect the other.

[hishutup]

huh... It may be because another program is running through MO like any SkyProc program... They seem to stick around.

 

I think I have seen this but it was because of exactly what I had described above... 

I believe it was DSR or ReProccer that kinda hang out for awhile

 

Try to remember the box that you click to unlock mo after running a program or don't click it at all.

It'll save you some headache

[enkephalin07]

ENB Host, maybe? It wasn't running either of the times I caught this, but it's not unusual for it to hang around doing clean-up before closing.

[hishutup]

no, ENB Host only runs when the dll calls it¹

Its likely to be a dynamic patch or maybe MO is just hanging out..

 

 

Tannin will likely be able to provide better help

 

 

*1--Yes, there is probably a more accurate explanation but I don't know it--

[enkephalin07]

no, ENB Host only runs when the dll calls it¹

Yes. That only happens every time Skyrim runs, unless something else has gone terribly wrong.

[Tannin]

The ModOrganizer.exe you see in the process list is really the UI of MO. If that is still around without a visible window that could have a few reasons.

a) the window is on a different screen (maybe not even connected). Don't fret, this happens

b) MO hangs at startup. One possible reason might be you had MO running and tried to start a download from nexus. This will start a second MO instance that should connect to the first, transmit the download url and then close again without a window (for that process) ever popping up. If, for unknown reasons, that second process fails to connect or something, it might remain alive.

c) MO hangs at shutdown. When you close MO it does a couple of things before it's actually gone, like ensuring all data files are saved. If any of that causes a hang (again: unkown reasons) MO might stay around without a window.

 

With the available information there is no way I could find the problem but if you can narrow down the situation under which this happens, please report that to the issue tracker.