-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
process may stay alive after quit #1645
Description
The process may stay alive after quitting the program. If the option "Start only a single instance of KeePassXC" is active, no restart is possible (unless u kill the process). Passwords may still be available in the browser (I can't reproduce anymore: once the proxy stayed alive, usually the proxy dies).
Expected Behavior
If I end the program I expect it to actually end all processes including the browser proxy. To clearify: ending the program must be possible all available ways to close the program: Ctrl+Q, menu, close button in window-header. kill -9 may not the usual way and probably this is not safe at all!
Current Behavior
Certain bugs may keep the process alive and thus prevent to start a new session and possibly keep passwords available.
Possible Solution
I will save my sarcasm for later.
Steps to Reproduce (for bugs)
- create a new entry with url "https://opentable.com" and hope retrieving the favicon still doesn't work
- try to download the favicon for the entry
- have "Start only a single instance of KeePassXC" in settings active
- quit the program
- ps -a | grep keepass
- try to restart
- try to access passwords from the browser plugin
Context
I tried to quit the application in order to fully clean up memory from my passwords.
Debug Info
KeePassXC - Version 2.3.0
Revision: 4c0ed74
Libraries:
- Qt 5.10.1
- libgcrypt 1.8.2
Operating system: Arch Linux
CPU architecture: x86_64
Kernel: linux 4.15.6-1-zen
Enabled extensions:
- Auto-Type
- Browser Integration
- Legacy Browser Integration (KeePassHTTP)
- SSH Agent
- YubiKey