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

Anytype leaves orphaned processes running after being closed (Windows) #718

Open
3 tasks done
Darthagnon opened this issue May 10, 2024 · 3 comments
Open
3 tasks done
Labels
bug Something isn't working

Comments

@Darthagnon
Copy link

Have you read a contributing guide?

  • I have read CONTRIBUTING.md
  • I have searched the existing issues and didn't find any that were similar
  • I have considered creating a pull request with fixes instead of a bug report and want to proceed

Current Behavior

If I disable Anytype from showing in the system tray and close it, it leaves 5 processes (250mb RAM) running orphaned in the background. Subsequent attempts to reopen Anytype fail, until I manually kill those processes with Task Manager/Process Hacker.
chrome_240510_61

Expected Behavior

If I disable Anytype from showing in the system tray and close it, I expect it to fully close and leave nothing running in the background.

Recommend renaming option Anytype >> Settings >> Show Anytype in system tray to Anytype >> Settings >> Run Anytype in background to more accurately reflect the expected and desired behaviour. System tray is for showing processes running in background, and hiding systray icons while still running is a dark pattern or a serious bug.

NB. Settings layout is also confusing.

Related issues: #630

Steps To Reproduce

  1. Run Anytype
  2. Goto Anytype >> Settings >> Show Anytype in system tray and disable it
  3. Close Anytype. There is no icon in systray to show it is still running, or to reopen the program to properly close it.
  4. Check in Task Manager/Process Hacker, and find 5 orphan processes still running. Anytype will not reopen until those processes are manually killed.
  5. There seems to be no way to properly close Anytype.

Environment

- OS: Windows 10

Anything else?

No response

@Darthagnon Darthagnon added the bug Something isn't working label May 10, 2024
@ra3orblade
Copy link
Contributor

Fixed in latest alpha.

@adhadse
Copy link

adhadse commented May 21, 2024

The latest alpha seems to crash before even loading the UI, and leaves orphaned process just like this on Linux.

@ra3orblade
Copy link
Contributor

Yes, cause latest alpha on the moment of writing the comment was different, the most recent one crashes and I didnt rebuild yet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants