Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GlosSiTarget fails to close when exiting from the game #35

Open
OdinIsLord opened this issue Dec 31, 2024 · 3 comments
Open

GlosSiTarget fails to close when exiting from the game #35

OdinIsLord opened this issue Dec 31, 2024 · 3 comments

Comments

@OdinIsLord
Copy link

OdinIsLord commented Dec 31, 2024

Please note that when exiting via the steam BPM overlay and not from the game itself, GlosSiTarget process is killed without problem. This only happens when closing from inside the game or emulator.

6vjXNKhlCY

Playnite shows that the game is no longer running but Steam still shows it as running and it will kill GlosSiTarget if I press STOP manually.

steamwebhelper_FSR64x0h19

So why is this a problem? If GlosSiTarget fails to close and you go on to open the same game or another integrated game, Playnite will freeze and stop responding until you kill the previous GlosSiTarget process. Then it will unfreeze and open said game with the overlay. That means if you use Playnite Fullscreen mode overlay and browse a game and try to launch it from there. GlosSiTarget will fail to close and Playnite will hang until you kill GlosSiTarget manually from Task Manager or Steam.

My current Windows version is 24h2 LTSC. This wasn't an issue when I was on 23h2 Iot Enterprise.

@OdinIsLord
Copy link
Author

So as I initially thought, this behavior happens only on 24h2. I went back to 23h2 due to numerous bugs and performance issues and this issue was resolved.

I suggest anyone wanting to upgrade to 24h2 not to do so.

@mbutera11
Copy link

mbutera11 commented Feb 25, 2025

@OdinIsLord Did this ever come back for you? I have this problem as well, and I'm using 23H2.

@OdinIsLord
Copy link
Author

@OdinIsLord Did this ever come back for you? I have this problem as well, and I'm using 23H2.

Yes, Idk if it was Microsoft porting 24h2 features to 23h2 via the monthly channel updates. I honestly gave up on it.

But this is not the extensions fault as this also occurs with the standalone GlosSi program, It seems to that the latest GlosSi version is force creating a global overlay of some sort on top of the individual one for each game.

@LemmusLemmus might be able to comment on it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants