Chrome bug makes some very popular extensions unusable for ~4% of users

A tale of spelunking through the depths of Chrome in search of an elusive bug affecting multiple popular extensions, including my company's optional extension

Hi folks!

It’s been a good long while since I last sent an update to this mailing list. Since the last one, I’ve posted a couple of technical articles and some recipes, but nothing I thought was big enough to warrant an email update.

I have something a bit juicier now, a bug in Chrome that makes extensions unresponsive. I and others on my team have spent the last 8 weeks trying to figure out, as it is affecting maybe 3-5% of our users and, as it turns out, users of several other very popular extensions.

I think you will enjoy it if you like to dig into technical stuff, or if you’re looking for one more reason to build on your own platform rather than somebody else’s.

Also, we’re offering a couple of $4K bug bounties for help tracking down this bug, in case you’re into that kind of thing.

Here’s the post: A Chrome bug affects 3-5% of users of 5+ popular extensions. Help hunt it down!

Cheers,
Jói