Re:The weirdest bug I've seen yet
by karmakaze on Thursday November 30, 2023 @08:01PM
(#38481567)
I was so disappointed that the story ended with we can't look inside Grammerly or Chrome to know why the gif decode/rendering causes it to crash. This isn't interesting at all. Many problems get narrowed down to some combination but not knowing really why is unsatisfying.
[ Parent
| on HN ]
It would be nice if the author would at least publish the .gif file. I want to dig into this.
Second this. Also, I'd like to know what was different in the new gif.
Re:The weirdest bug I've seen yet
by jsunderland323 on Thursday November 30, 2023 @11:59PM
(#38483316)
Agreed. I was on the edge of my seat. I wouldn’t do a write up for something like this. I feel no-soap radio’d.
TIL: Thanks for that. https://en.wikipedia.org/wiki/No_soap_radio
The Chromium source code is also available, not sure why they said they couldn't look at it. If it replicates with Chromium you can dig right in.
If you read carefully you will see that they said the bug didn’t replicate with Chromium
They did yeah, but did they try Chromium with Grammarly?