You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Yes, I tried searching and reviewed the pinned issues
Brief Summary
Windows 10 system: 22H2
KeePassXC V2.7.9
MSVC 14.42.34433
It's suffering the crash bug that's been reported elsewhere, but this can't be an out-of-date MSVC, because I have verified that the latest version: 14.42.34433 is installed. I did a complete uninstall of MSVC, rebooted, installed 14.42.34433, rebooted again, and only then started KeePassXC.
So, what I would like to ask is what steps I can take to help identify the issue. For example, is it possible to get a full debug build (MSVC /Zi option), and the corresponding PDB file, so I can run the program under VS2022 and try and catch what's going on when it exits. Yeah, I know the debug version will be a lot bigger and a lot slower. I'm willing to work with those limits to help get this sorted out.
Failing that, I've checked in C:\Users<username>\AppData\Local\and I can't see a crashdumps folder in there. Is there something I can do to turn on the generation of a crash dump file, which I can either attach to this issue, or open up in VS 2022, again with PDB and source, to try and get a clue what's going on.
Any other suggestions for things I can do to help identify this will be most welcome.
My thought process is that this is probably going to be impossible to reproduce for the development team, so I'm the only person that can debug this, thus my reason for asking how I can help.
Steps to Reproduce
Install Windows 10 22H2
Install MSVC 14.42.34433
Run KeePassXC
Expected Versus Actual Behavior
No response
KeePassXC Debug Information
KeePassXC - Version 2.7.9
Revision: 8f6dd13
Qt 5.15.11
Debugging mode is disabled.
Operating system: Windows 10 Version 2009
CPU architecture: x86_64
Kernel: winnt 10.0.19045
Enabled extensions:
- Auto-Type
- Browser Integration
- Passkeys
- SSH Agent
- KeeShare
- YubiKey
- Quick Unlock
Cryptographic libraries:
- Botan 3.1.1
Operating System
Windows
Linux Desktop Environment
None
Linux Windowing System
None
The text was updated successfully, but these errors were encountered:
You will have to build from scratch using vs 2022, we have instructions posted on our wiki. Recommend just running one of our snapshot builds to confirm if the problem has already been resolved: https://snapshot.keepassxc.org
Have you searched for an existing issue?
Brief Summary
Windows 10 system: 22H2
KeePassXC V2.7.9
MSVC 14.42.34433
It's suffering the crash bug that's been reported elsewhere, but this can't be an out-of-date MSVC, because I have verified that the latest version: 14.42.34433 is installed. I did a complete uninstall of MSVC, rebooted, installed 14.42.34433, rebooted again, and only then started KeePassXC.
So, what I would like to ask is what steps I can take to help identify the issue. For example, is it possible to get a full debug build (MSVC /Zi option), and the corresponding PDB file, so I can run the program under VS2022 and try and catch what's going on when it exits. Yeah, I know the debug version will be a lot bigger and a lot slower. I'm willing to work with those limits to help get this sorted out.
Failing that, I've checked in C:\Users<username>\AppData\Local\and I can't see a crashdumps folder in there. Is there something I can do to turn on the generation of a crash dump file, which I can either attach to this issue, or open up in VS 2022, again with PDB and source, to try and get a clue what's going on.
Any other suggestions for things I can do to help identify this will be most welcome.
My thought process is that this is probably going to be impossible to reproduce for the development team, so I'm the only person that can debug this, thus my reason for asking how I can help.
Steps to Reproduce
Expected Versus Actual Behavior
No response
KeePassXC Debug Information
Operating System
Windows
Linux Desktop Environment
None
Linux Windowing System
None
The text was updated successfully, but these errors were encountered: