News for hackers. Stuff that matters.
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.
Re:The weirdest bug I've seen yet by chatmasta on Thursday November 30, 2023 @11:07PM (#38483014)
It would be nice if the author would at least publish the .gif file. I want to dig into this.
Re:The weirdest bug I've seen yet by iamcreasy on Friday December 01, 2023 @09:06PM (#38495154)
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.
Re:The weirdest bug I've seen yet by karmakaze on Saturday December 02, 2023 @05:22PM (#38502732)
Re:The weirdest bug I've seen yet by jolux on Friday December 01, 2023 @12:45AM (#38483581)
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.
Re:The weirdest bug I've seen yet by rhaps0dy on Friday December 01, 2023 @12:47AM (#38483593)
If you read carefully you will see that they said the bug didn’t replicate with Chromium
Re:The weirdest bug I've seen yet by rezonant on Friday December 01, 2023 @02:33AM (#38484154)
They did yeah, but did they try Chromium with Grammarly?
Re:The weirdest bug I've seen yet by jolux on Monday December 04, 2023 @10:49PM (#38526898)
They say it didn't replicate in Chromium but that's before they figured out what it was.