@sohkamyung So if anyone’s still following this, it turned out to be an experimental configuration setting in Chrome that Google turned on remotely for A/B testing.
Basically they have features that aren’t quite ready, but that they put in the release version of the browser behind a config setting, and when the browser launches, it checks a server-side list of which experimental features it should turn on or leave off.
I can understand the logic, but it’s also creepy.