Autofill overlay doesn't work on macOS

[rghedin]

Description When I summon the autofill screen on Safari, Keepassium overlay doesn't work. It appears, but I can't click on anything. I can't even dismiss the overlay — for that, I need to press Esc twice.

How to reproduce

1. Go to a login form and select Keepassium;
2. Kepassium overlay will open;
3. Can't click on anything.

Expected behavior That buttons are clickable.

Screenshots https://user-images.githubusercontent.com/19216581/167126103-94e6534d-53b7-4751-81b3-022a703c1b7d.mov

Environment:

• Device: MacBook Pro (early 2015)
• OS: macOS 12.3.1
• App Version: 1.32.110

[rghedin]

An update.

I restarted Safari and the overlay is working fine again. Not sure what triggered it to became non-responsive, but I'll keep an eye on it.

[keepassium]

Thanks! Yeah, this happens sometimes, randomly (?) and I've been struggling to figure it out (or reproduce reliably). Interestingly, keyboard still works: you can close AutoFill by pressing Esc.

This was also reported on Reddit, and one of the comments suggested steps to reproduce:

I can reproduce it every time. this usually happens on MacBook Pro M1Pro after Safari is idle for some time. i think after the Mac goes to slip and the lid is closed.

In your case, does the issue also happen after the Mac wakes from sleep?

[rghedin]

In your case, does the issue also happen after the Mac wakes from sleep?

I left my MacBook Pro (Intel-based) asleep last night. Just tested in the morning and it's still working fine, so, no, sleeping probably isn't the cause.

I saw a related issue that may have de same root: sometimes, LinkedIn website just stop opening. When I try loading it, it hangs eternally in a blank page, and only got back if I fully close and reopen Safari — the same solution I found for Keepassium's issue.

[keepassium]

Thanks for testing! So the mystery remains…

At the moment I can offer only a slightly faster workaround: can terminate "KeePassium AutoFill (Safari)" process via Activity Monitor, no need to restart Safari.

[adlpz]

Posting here to confirm that as of today this issue remains. My workaround is keeping a bash script handy that kills Keepassium whenever this happens.

Is there anything we can provide you to make debugging easier?

Happy paying customer by the way, thanks for the amazing app :)

[keepassium]

My workaround is keeping a bash script handy that kills Keepassium whenever this happens.

@adlpz, thank you! Making an app that people use is one thing. Making an app that people create-workarounds-to-use-despite-its-bugs feels like an accomplishment, oddly enough :)

Is there anything we can provide you to make debugging easier?

A reliable way to reproduce the issue would help tremendously. Without it, I need to test every hypothesis for a week only to have a probabilistic answer in the end ("maybe solved" or "definitely remains"). Which is so inefficient that I don't really want to go that path…

[keepassium]

I was poking around trying to reproduce the issue, and it just happened — randomly, though :) But there are some potentially useful nuggets:

• Safari was already running with AutoFill responsive. The issue happened randomly after some switching between windows/desktops. The machine did not sleep.
• The memory footprint of the AutoFill module was fine, around the same as when it was responsive.
• Once AutoFill became unresponsive (to mouse events), it was possible to type in the search bar. Notably, it was also possible to open a new Safari window and open AutoFill there — though it was also unresponsive.
• Most importantly: I tried turning off-then-on the display, and AutoFill became responsive again. The machine is a Mac Mini with a single display.

Can anyone test/confirm the last one, please?

[adlpz]

@keepassium I can confirm, last time it froze I disconnected the external display (on a Macbook Air M1) and it became responsive again.

Tried moving it between screens. Did not solve the issue.

After that, even if the display is plugged back in, the app functions normally, until it freezes again.

[keepassium]

After upgrading to 13.2.1 a couple of weeks ago, I have not encountered this issue at all, not once. Is it just me?

[adlpz]

@keepassium I was on the same boat, no issues for a while, but it just happened again! And, as before, I disconnected the external display on my Macbook and worked again.

So, it's still there :(

[keepassium]

@adlpz, thanks! And I was just about to close the issue… :)

On the positive side, it got better. Moreover, it got better without any changes in KeePassium — which supports the hypothesis that this is a system issue.

[keepassium]

Has anyone encountered this on macOS 14 Sonoma?