LastPass among affected
So Google has finally came up with a replacement?
For the past three months, an elusive bug in Google's open-source Chromium project has been causing a small percentage of Chrome extensions to silently fail. The bug affects about three to five percent of users of several popular Chrome browser extensions, according to Jói Sigurdsson, founder and CEO of CrankWheel, maker of a …
It could as easily be a bug in the page. IIRC, thanks to the magic of threads, the browser can appear responsive while the page is blocked. Or it might have "debounce" logic that has failed. (Something threw and it didn't catch it? Or async code never returned at all?) Or something could have erroneously swallowed the event. Or it could have accidentally set `pointer-events:none`. And so on.
In short there are a myriad things that could go wrong. The first step would be to open the web inspector and see was happening.
I have an exciting collection of CCD images of cosmic rays at various interesting angles from head on blobs to near horizontal traces. Earthbound, too. This was back when CCDs needed to be cooled and not everybody had multiple devices in their phones...
FWIW, I think you could update your error mechanism to a disturbance caused by an unintentional, row-hammer-style bit flip.
Biting the hand that feeds IT © 1998–2022