Super-productivity: Windows app suddenly uses all the system memory, closing the app doesn't release them

[Looooong]

Your Environment

• Version used: 5.9.9
• Operating System and version: Windows 10 version 2004 build 19041.508
• Desktop Environment:
• Browser Name and version:

Expected Behavior

There should be an option to really quit the app, release all the memory used by the app.

Current Behavior

This is the first time I saw it suddenly consumed all the memory and disk usage. Closing the app doesn't release the memory. The app is instead moved to the background.

Steps to Reproduce (for bugs)

1.
2.
3.
4.

Console Output

Error Log (Desktop only)

[johannesjo]

Thanks for reporting. This is weird. I never encountered this on windows before and I can't reproduce this. Can you consistently reproduce the issue? And are you using the pen drive version or the setup.exe?`

[johannesjo]

Very likely related: #493

[Looooong]

I only experience this issue once yesterday. And I forgot to check the console before killing the app. So I don't know how to reproduce this issue. The features I used in the app yesterday are:

• Start/stop tracking task using global hotkey.
• Open/close the app using global hotkey.
• Synchronize to Google Drive.
• Track a task for 9.5 hours.
• Modify spent time on task.

I think that you should work on the second problem, where is no mechanism to really kill the app, except for using Task Manager.

[johannesjo]

Should have said it more explicitly but that's what I was talking about:

1. If you close the app does it always, is it always still in the task manager?
2. Are you using the pen drive version or the installer setup.exe?

[Looooong]

If I close the app, either by clicking the X button or selecting Close via system tray, the app will go to the background process list, and the memory is not released at all.

I use the Windows Store version.

[johannesjo]

Ah thanks! That's interesting. Haven't tested the store version for this issue to be honest. I'll check what might be causing this.

[johannesjo]

The windows store version also closes fine in my tests. However, I found this suggestion. If it doesn't fix the issue it might at least provide a little more insight, why this might be the case.

[johannesjo]

I'll make a new pre-release shortly (available as a download here as version 5.9.15.). Could you check with it, if this still occurs?

[Looooong]

I have just taken a look at how the app is closed again. Under normal circumstance, the app is removed completely from the process list. So I guess that the memory problem back then prevented the app from closing fully.

[johannesjo]

Yes, it seems like it. I would very much appreciate it if you could keep an eye out on when this happens (if it happens again). I really can use all information I can get. There is also a little performance monitor included in the app. You can access it by opening up the dev tools (Ctrl+Shift+i), clicking the little three dots on the top right of the new window and then go to "More Tools/Performance Monitor".

[Looooong]

Sure, I will keep it in mind next time.

[thetric]

I encountered this closing bug under Linux too.

• Version: 5.9.15-SNAPSHOT, Commit 1d37e0a (based on PR https://github.com/johannesjo/super-productivity/pull/501)
• OS: Arch Linux (5.8.12-arch1-1), 64 bit

Repro:

• yarn buildAllElectron:noTests:prod && electron-builder --linux
• ./app-builds/superProductivity-5.9.15.AppImage
• close the app

Can be reproduced without previous backups (no .config/superProductivity folder)

[johannesjo]

@thetric thanks! I'll try to check this tomorrow.

[johannesjo]

@thetric For 5.9.15 I think I broke it with 5e340ad. After 4f5212f I am unable to reproduce this for the AppImage. Could you please confirm if it is working for you with 4f5212f as well?

[thetric]

Looks good to me. The app is closed as expected