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

Background processes remain when closing desktop app #8198

Open
x3003 opened this issue Dec 25, 2024 · 10 comments
Open

Background processes remain when closing desktop app #8198

x3003 opened this issue Dec 25, 2024 · 10 comments
Labels
bug broken functionality, usability problems, unexpected errors desktop Desktop client related issues

Comments

@x3003
Copy link

x3003 commented Dec 25, 2024

Describe the bug
After closing the desktop app, there are still 3 background processes, for each time you start the app. After running the app a few times, the processes only get more and more. After a few hours, you might even get a high cpu usage.

To Reproduce
Steps to reproduce the behavior:

  1. Start Desktop App in Windows.
  2. In Settings, change "Run in background" to No
  3. Close app.
  4. After closing app, 3 background processes will remain.

Expected behavior
That all processes quit

Screenshots
tuta_bug

Desktop (please complete the following information):

  • Win 10 x64 home, up-to-date
  • Tuta v259.241223.2
@x3003 x3003 added bug broken functionality, usability problems, unexpected errors desktop Desktop client related issues labels Dec 25, 2024
@jackwilliams79
Copy link

I'm experiencing the same issue but on Linux (Fedora 41)

Tuta Desktop Version: v259.241223.2

After closing the Desktop app completely, one process (tutanota-desktop) remains running and causes the fans of my laptop to spin on full speed. Only after manually killing the remaining process the fans will slow down again.

@jiravatt
Copy link

Same here, on macOS 15.2.
(Desktop version 259.241223.2)

@user7901
Copy link

user7901 commented Dec 26, 2024

same issue Windows 11 (Tuta [259.241223.2 Desktop)
tuta

@KevinW1
Copy link

KevinW1 commented Dec 27, 2024

Same thing on Ubuntu 22.04. Tutanota desktop appimage v259.241223.2
Each instance is taking a significant amount of cpu to the point where if I have 10 of them my machine becomes quite slow. I tried leaving it for 12 hours or so and they never finished or closed whatever they were doing/waiting for.
Screenshot from 2024-12-27 00-31-52

@HubbyG
Copy link

HubbyG commented Dec 28, 2024

Same here endeavour os (arch) and Tuta desktop 259.241223.2
Tuta desktop Integrated but not set to run in background.

Tuta stays in background and occasionally (half the time) uses high cpu. Have to manually KILL

@0-5-0
Copy link

0-5-0 commented Dec 29, 2024

Same issue, I don't normally leave Tuta running (I launch it when I need it), PC was crawling, restarted, opened Tuta and closed it but saw multiple tutanota-desktop processes were still running when checking htop with 1 tutanota-desktop process eating 1 CPU core at 100% even 15 minutes after closing the app.

A fresh PC reboot or not makes no difference, I launched Tuta again, closed it after it logged in and did it's new message check, now there's 2 tuta processes eating 2 CPU cores at 99/100%. SigTerm doesn't stop them, only SigKill and launching a new Tuta instance then closing it the issue repeats again.

I'm on the latest EndeavourOS using the Tuta desktop appimage v259.241223.2.

Run in background: No
Run on startup: No
Desktop integration: Deactivated
Automatic Updates: Activated

@hrb-hub
Copy link
Contributor

hrb-hub commented Dec 30, 2024

This issue seem to occur in versions >= V259.241223.1
Logs from a Mac were provided in #8199 (comment)

@reset131
Copy link

reset131 commented Dec 31, 2024

The behaviour is a slightly different, it was well represented in a previous post which is now closed (#8210) The application does not quit, you have to force quit. This seems to be a macOS only bug. I'm on 12.7.6, but it seems to happen on all Macs systems.

@schwafe
Copy link

schwafe commented Dec 31, 2024

I was wondering why my laptop was so loud and discovered Tuta being the culprit. I tried to recreate it: After opening and closing Tuta Desktop four times, I watched all instances first go down to 0 % CPU usage and after some time one became active again, rising to around 20 %. A short while later another became active and they started to show the same activity pattern (rising and falling in sync between 17 and 22 % CPU usage). Probably the others would also become active, if I gave them more time, but I'm not sure whether they would stop or pause by themselves.

V259.241223.2 on Windows 11
Run in background: No
Run on startup: No

@KevinW1
Copy link

KevinW1 commented Dec 31, 2024

259.241213.0 (Desktop) Is the latest version which reliably quits all processes for me.

kibibytium added a commit that referenced this issue Jan 3, 2025
if desktop client does not run in tray

partial fix for #8198

Co-authored-by: sug <[email protected]>
kibibytium added a commit that referenced this issue Jan 3, 2025
either immediately or after importing current chunk.

closes #8198

Co-authored-by: sug <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug broken functionality, usability problems, unexpected errors desktop Desktop client related issues
Projects
None yet
Development

No branches or pull requests

10 participants