-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Getting "Quit unexpectedly" message after quitting KeePassXC #1543
Comments
I originally observed this bug on the 2.3.0 beta download, but I was able to reproduce it with the non-beta release of 2.3.0. |
I've also experienced this issue or something similar when using the 2.3.0 beta. |
I did fix a crash in the beta, but it was not related to start-up |
I've rechecked; it crashes after I close KeePassXC with the database unlocked.
|
Can you test if it also happens if you compile 2.3 yourself? The program crashes somewhere in the Qt application / Cocoa drawing routines. |
On MacOS High Sierra I had crashes when closing custom build KeePassXC from commit 698b44f There are two thinks I've done which somehow fix it:
I believe the 2nd point is the key as I'm unable to reproduce the crash even with the 698b44f build. Before the mention steps the crash was reproducible 100% of the time
|
We saw this crash sporadically when using the prebuilt binary of the release version (KeePassXC-2.3.0.dmg) on macOS 10.2.6. I think the circumstances were: I was able to reproduce the issue using OP's workflow. Both with the newly created file and on subsequent attempts with the same file. |
I got the same issue with MacPorts' Qt. I guess this is not a Homebrew- or MacPorts-specific issue but a Qt one. I've rebuild Qt with MacPorts' debug option. Now I have QtFoo and QtFoo_debug libraries. However, keepassxc always links to the non-debug version QtFoo. Any idea how to link to the debug version QtFoo_debug? |
You need to set |
For me it is pretty consistent:
Result:
|
I bisected, and it appears that commit 806248e ("Review fixes") causes this. I searched a bit in the Qt bug database, and this looks slightly related, but I'm unsure: https://bugreports.qt.io/browse/QTBUG-54832 |
I submitted a fix for review. |
@phoerious, works fine for me. Thanks. |
Great. |
This issue/bug doesn't seem to have any actual negative effects (e.g. no database corruption that I found), but it is a bit unnerving to see an "quit unexpectedly" error.
Expected Behavior
KeePassXC should be able to quit without an error message.
Current Behavior
After unlocking and locking a database, if user quits KeePassXC, a few seconds later user receives an error message saying KeePassXC quit unexpectedly.
Steps to Reproduce (for bugs)
Opening the database and following steps 5 through 7 with KeePassXC 2.2.0 does NOT result in this error message being displayed.
Also, when using 2.3.0, if I just launch KeePassXC, then quit it without unlocking a database, I do NOT get the error message after quitting.
Context
As I stated above, I haven't created any database corruptions or even unsaved database changes with this bug. I just think it's something that, if reproducible, should be fixed before 2.3.0 leaves beta.
Debug Info
KeePassXC - Version 2.3.0
Revision: 4c0ed74
Libraries:
Operating system: macOS High Sierra (10.13)
CPU architecture: x86_64
Kernel: darwin 17.4.0
Enabled extensions:
Apple Error Information
Here is the first part of the text I got when I hit the "Report..." button on the error message.
The text was updated successfully, but these errors were encountered: