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

On macOS, quitting w3champions doesn't kill flo-worker #32

Open
frozenspider opened this issue Nov 22, 2024 · 1 comment
Open

On macOS, quitting w3champions doesn't kill flo-worker #32

frozenspider opened this issue Nov 22, 2024 · 1 comment

Comments

@frozenspider
Copy link

As the result, flo-worker keeps running. Restarting w3champions application a few times lead to multiple flo-worker processes running in background simultaneously.
(Additionally, closing w3champions window does not automatically quit the app)

@BogdanW3
Copy link
Member

BogdanW3 commented Nov 23, 2024

Closing the window shouldn't close the app, it should continue running in the taskbar, but not closing flo-worker is an issue as you said, keeping this open for someone to maybe look into it in the future, although this should be in the old launcher repo issues

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