3 ms·

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 int

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.

chatmasta 3y ago
It would be nice if the author would at least publish the .gif file. I want to dig into this.
- iamcreasy 3y ago
  Second this. Also, I'd like to know what was different in the new gif.
jsunderland323 3y ago
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.
- karmakaze 3y ago
  TIL: Thanks for that. https://en.wikipedia.org/wiki/No_soap_radio https://en.wikipedia.org/wiki/No_soap_radio
jolux 3y ago
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.
- rhaps0dy 3y ago
  If you read carefully you will see that they said the bug didn’t replicate with Chromium
  - rezonant 3y ago
    They did yeah, but did they try Chromium with Grammarly?
  - jolux 3y ago
    They say it didn't replicate in Chromium but that's before they figured out what it was.