Keepassxc: Windows Memory Error

[tinokorth]

Overview

On my PC at work and my laptop at home I get windows error messages that KeePassXC tries to allocate an unknown memory address (see screenshot).

Steps to Reproduce

There is no way to really reproduce the problem. Sometimes the problems occurs 3 times a day and sometimes KPXC works fine for a few days.

Actual Behavior

Windows shows an error window that KeePassXc.exe tried to allocate an address that is not available:

KeePassXC - Version 2.6.2
Revision: e9b9582

Qt 5.15.1
Diagnosemodus ist deaktiviert.

Betriebssystem: Windows 10 Version 2004
CPU-Architektur: x86_64
Kernel: winnt 10.0.19041

Aktivierte Erweiterungen:

• Auto-Type
• Browser-Integration
• SSH-Agent
• KeeShare (bestätigtes und unbestätigtes Teilen)
• YubiKey

Kryptographische Bibliotheken:
libgcrypt 1.8.6

[droidmonkey]

Are you using the browser extension when this happens?

[ninjaneteng]

I just opened bug 5675, and then saw yours. Is your situation the same? Read through my bug and see if it fits your situation also.

[ncaos]

I can only imagine we're all having the same issue for many weeks/versions now. It is not fixed in the latest extension version either (1.7.3). I'm using Vivaldi but I'm sure it's affecting all Chrome users in general. Not sure if it's affecting Firefox users.

For me, it is easily replicated on Google's shitty login pages. It will happen when the extension attempts to get the data, automatically or manually.

Seems likely it's https://github.com/keepassxreboot/keepassxc/issues/5596, or similar.

[droidmonkey]

This has nothing to do with the extension, its the application side.

[maartenmachiels]

Got the exact same issue here... The issue persists in Firefox and in Chrome. Thanks for looking into this and thanks for your great reboot of this software.

[tinokorth]

I can only imagine we're all having the same issue for many weeks/versions now. It is not fixed in the latest extension version either (1.7.3). I'm using Vivaldi but I'm sure it's affecting all Chrome users in general. Not sure if it's affecting Firefox users.

For me, it is easily replicated on Google's shitty login pages. It will happen when the extension attempts to get the data, automatically or manually.

Seems likely it's #5596, or similar.

Yes, it was the same issue. Sorry - I did not found this issue so I opened a new issue.