OpenCAGE shows "running" in Steam until Unity is exited

[ghramsey]

I've noticed this is happening recently. Level viewer closed and exit opencage but Steam reports opencage as 'running' and cannot relaunch, verify or anything else until I exit Unity completely by closing the tray icon.

If I try to force quit OpenCAGE is shows "closing" and probably would if I leave it long enough, but after 10m it remains stuck in that state. I didn't know what caused the issue. Now that I do I don't need to force it. It also leaves the task manager when it is in this state.

If I close Unity it closes opencage normally though.

I also noticed that when I exit the commands editor if the unity scene is open it closes rather abrupty.
Unity throws a warning on next use that it didn't close properly.

Not sure if those are related or not but might be.

For now the work around to the stuck condition is to close unity so it's not really a big issue.

[MattFiler]

Huh yeah good spot, I guess Unity is launching some sub-process that OpenCAGE forgets to kill when it's closing. I'll have a further poke - thanks.

[MattFiler]

Ah, it appears Unity Hub starts as a tray service when launching Unity if you have Hub installed, which Steam mistakenly links to the OpenCAGE process. If you uninstall Unity Hub this may resolve the issue, but I'll look at getting a fix for users who have this set-up.

[ghramsey]

I uninstalled the Unity Hub leaving the main Unity component in place.
The Hub is actually unneeded with the commands editor now doing all the install scripting. I have two scenes for Epic and Steam, but vast majority of users will probably have it only on Steam.

That seems to work. Unity closes the scene process when the commands editor closes.

It seems to be soft-closing now too. Unity is not complaining about improper shutdown or doing any cleanup before launching the scene again.

So the ultimate work around is to just uninstall or not install Unity Hub at all.