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)

1. Download KeePassXC 2.3.0 beta from Github
2. Verify DMG sig, install, launch application, created new database. Add a test entry.
3. Lock db and quit KeePassXC
4. Launch KeePassXC, either by launching the application or double clicking on your new database.
5. unlock database.
6. Lock database
7. Quit KeePassXC
8. In a few seconds, get this unnerving message

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:

• Qt 5.9.3
• libgcrypt 1.8.2

Operating system: macOS High Sierra (10.13)
CPU architecture: x86_64
Kernel: darwin 17.4.0

Enabled extensions:

• Auto-Type
• Browser Integration
• Legacy Browser Integration (KeePassHTTP)
• SSH Agent
• YubiKey

Apple Error Information

Here is the first part of the text I got when I hit the "Report..." button on the error message.

Process:               KeePassXC [1017]
Path:                  /Applications/KeePassXC.app/Contents/MacOS/KeePassXC
Identifier:            org.keepassx.keepassxc
Version:               2.3.0 (???)
Code Type:             X86-64 (Native)
Parent Process:        ??? [1]
Responsible:           KeePassXC [1017]
User ID:               501

Date/Time:             2018-02-27 20:27:05.318 -0500
OS Version:            Mac OS X 10.13.3 (17D102)
Report Version:        12
Anonymous UUID:        [Redacted in case sensitive]


Time Awake Since Boot: 3600 seconds

System Integrity Protection: enabled

Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       EXC_I386_GPFLT
Exception Note:        EXC_CORPSE_NOTIFY

Termination Signal:    Segmentation fault: 11
Termination Reason:    Namespace SIGNAL, Code 0xb
Terminating Process:   exc handler [0]