Jonathan Wildstrom

I don't even know how I'd do that, nor what I'd be looking for. I have Visual Studio Code, but not a full version of Visual Studio. I'm willing to try if you can give me some instructions, though. Is there any possibility it's just EXITTING in some weird path, but not crashing?

IT looks like it crashed again, but I don't see anything in those directories. Anywhere else I should check?

Is there any harm in running that in general? I.e., if I restart (I figure I should after running the various stuff above) start keepass, and run that, will it cause any issues? If not, it seems like I might as well get the information on the first crash.

OK, ran all those, I'll see what happens with crashes for the near future.

And I just got another crash, no plugins at all. So....next steps for debugging?

Crud, I spoke to soon. Just crashed sometime today. I'll pull the last plugin now.

OK, SO far (this is still pending changes) removing KeePassWinHello did not resolve the issue. Removing KeePassRPC as well has so far not crashed. Of course, not having that is annoying, but I can work around it. I'll give another week, and if I still have no crashes, I can probably say it's that one (or an interaction between that an KeeAutoExec, I guess). Then I can try putting WinHello back. Of course, I still don't know if that plugin is responsible or just exercises a problematice code path...

I can do that, but it'll be a real nuisance, since it'll happen anywhere from once a day to every few weeks, and the normal way I use it involves it locking regularly (I have 5 databases) and auto-filling fields on Chrome. I'm actually going to try PULLING the plugins one at a time, and see if one makes the problem go away, since disabling WinHello is easy (Typing the password each time is only a minor nuisance), RPC is a little harder (I'll have to copy the passwords) and AutoExec is basically a...