search

TheGoddessInari / hamsket

Free and Open Source messaging and emailing app that combines common web applications into one.
GNU General Public License v3.0
880 stars 55 forks source link

Leak of CPU & RAM usage/ressources after closing Hamsket #335

Open pokemaster974 opened 2 years ago

pokemaster974 commented 2 years ago

Steps to reproduce

  1. Open Hamsket
  2. Wait
  3. Close Hamsket

Expected behavior

Kill all hamsket.exe

Actual behavior

Sometimes, closing Hamsket won't kill process Screenshot represent ressources taken by Hamsket after closing via GUI (and not in system tray) and result of CPU & RAM usage after closing via task manager all remaining process Hamsket (1) Hamsket (2) Hamsket (3)

ENVIRONMENT

Hamsket: v0.6.3 OS: Windows 10 Arch: x64 BuildVersion: 0c6cda4 (grafted, HEAD, tag: nightly, origin/0c6cda40ac26dcdd591adc39428fe6c411c1b604) Thu, 9 Dec 2021 18:30:29 -0800

TheGoddessInari commented 2 years ago

Please try with a newer version.

When this sort of thing occurs, it's (as far as I can tell at the moment) usually an Electron bug on Windows, as Hamsket should not functionally do anything in close/quit hooks that can hang or block. I triple-checked again.

pokemaster974 commented 2 years ago

In fact, this bug is present since several versions. Don't remember the first version of Hamsket I use but it's already here. Just haven't time to report it. FYI, I've tried to uninstall/reinstall Hamsket (after deleting %AppData% folder). I even do a clean reinstall of Windows (for other reasons) and reinstalling Hamsket without importing something but bug stills here.

0.6.3 is the last version I found. Do you want I try the nightly version or another version ?

pokemaster974 commented 2 years ago

Windows' clean install + Hamsket's nightly I don't know what to do more...

Hamsket0

01