I came across this issue as well, on Saturday afternoon, it is quite annoying. I didn’t end up submitting a bug report, as I concluded this was actually an issue within Chromium (I have a performance profile report that shows this if an engineer is interested), specifically in Omnibox. It appears to be fixed in newer builds of Chromium and doesn’t even occur within Firefox/Safari, so hopefully a fix will be more widely available soon.
(CC: @NightTheChosen)
What version of Chrome are you on? (See chrome://settings/help). I can’t reproduce this on the latest stable versions of Edge or Chrome.
I’m also not sure these are related issues either, unless your browsers are fairly out of date, the fixes that caused this have been out for weeks on Chrome/Edge.