The weirdest bug I've seen yet
engineering.gusto.com
The weirdest bug I've seen yet
1–10 of 334 posts
Re: The weirdest bug I've seen yet
#2Such a tease. At least upload the gif so people can poke at it!
Re: The weirdest bug I've seen yet
#3Such a tease. At least upload the gif so people can poke at it!
Agreed!
I have absolutely no idea how a combination of grammarly and a specific gif would cause a browser crash though…
Anyone here use the grammarly desktop app? Any additional clues?
Re: The weirdest bug I've seen yet
#4Well, this is a fascinating murder mystery that establishes 3 compelling suspects - Grammarly, Chrome, and a gif - and then just ... ends, right before the big reveal.
Re: The weirdest bug I've seen yet
#5Hash collision?
Re: The weirdest bug I've seen yet
#6Is there a copy of the gif available? That’s interesting
Re: The weirdest bug I've seen yet
#7Well, this is a fascinating murder mystery that establishes 3 compelling suspects - Grammarly, Chrome, and a gif - and then just ... ends, right before the big reveal.
I have a friend who worked at Gusto, and my wife tried using Gusto for her small business (they handle payroll for small business, got a big boost from the pandemic). The lack of technical resolution here is so Gusto, it hurts.
Re: The weirdest bug I've seen yet
#8> For security reasons, we do not have Chrome crash reporting enabled.
> We also confirmed with many of our affected users that they had Grammarly installed on their computers.
Ironic.
Re: The weirdest bug I've seen yet
#9Well, this is a fascinating murder mystery that establishes 3 compelling suspects - Grammarly, Chrome, and a gif - and then just ... ends, right before the big reveal.
I feel so unsatisfied
Re: The weirdest bug I've seen yet
#10> Unfortunately, with access to neither the Chrome source code
I mean, you basically do! You can just go check out the chromium source.