Raúl Núñez de Arenas Coronado

Yes, I'm using Chrome 95. The list is populated slowly without --force-renderer-accessibility, but with it enabled it happened too: the active tab was found fast, but after a tab switching the list didn't reflect the change and the updating was slow, too. I don't have any extensions in Chrome apart from Chrome Remote Desktop (inactive) and Google Drive App Menu (inactive, too), and usually I have a couple tabs opened. I mean, sometimes when working I can have even 20-30 tabs opened, but right now...

Before testing the new version, I have to tell you that you NAILED IT! Effectively, the problem was the list was taking ages to populate, probably more than one minute in this otherwise fast computer. And the problem was caused by Chrome (probably Edge will cause the problem, too). Chrome active tab can be obtained even if launched without --force-renderer-accessibility, but the dropdown list was taking too long to populate. Funnily enough, when the list was finally populated, any tab switching caused...

Before testing the new version, I have to tell you that you NAILED IT! Effectively, the problem was the list was taking ages to populate, probably more than one minute in this otherwise fast computer. And the problem was caused by Chrome (probably Edge will cause the problem, too). Chrome active tab can be obtained even if launched without --force-renderer-accessibility, but the dropdown list was taking too long to populate. Funnily enough, when the list was finally populated, any tab switching caused...

OK, now KeePass 2 does not crash as frequently, but it crashes. Took me a few tries but it crashed. I'm attaching the new logs, just in case. On the other hand, the dropdown tests were as follows: - Firefox: the dropdown works, and adding a new entry works, too. Switching tabs properly updates the URLs shown in the new entry when the hotkey is pressed. - Chrome, launched with --force-renderer-accessibility: the dropdown only shows the active tab, and adding a new entry works. If tabs are switched,...

Windows 10, 21H1, build 19043.1320. I've set things up and tried what you suggested. It fails for Chrome and Edge, works for Firefox. If fails for Chrome EVEN launching Chrome with --force-renderer-accessibility. After this test I tried again and the dropdown again causes a crash. I could not locate the crash logs for KeePass BUT it appears in my Event Viewer, where it appeared as TWO errors, one in KeePass 2 itself, the other in the .NET runtime. I'm attaching the XML versions of the two errors....

URL drop down does not work with any browser and makes KeePass 2 crash

Well, at any rate, you made me think of some use cases that somewhat justfied the password column to be obfuscated, so thanks anyway, T.Bug! :-)

Sorry for the delay in replying to this thread, I couldn't do it before. First of all, thanks A LOT for your fast response, @Paul. Second, I didn't have an enforced config file, but for some reason that particular node was not being saved. I edited the XML by hand, removed the node, started the program, modified the visible colums, and then exited and it worked, it saved the config correctly. Thanks a lot, Paul, I couldn't find the node I had to change. Third, I have to agree with Paul and not with...