I am using chromium to print web pages to pdf, and I have some images that will crash chrome's to pdf process, I found nothing wrong with this images, the metadata is fine (nothing weird in it). The other bad thing it does not reproduce n my dev machine only on the production server , so nothing I can do, in rare cases an image will always crash crhomium, I find it, open it and re-export it and then it works.
The weirdest bug I've seen yet
11–20 of 334 posts
Re: The weirdest bug I've seen yet
#12> Unfortunately, with access to neither the Chrome source code I mean, you basically do! You can just go check out the chromium source.
> I mean, you basically do! You can just go check out the chromium source.
It's mentioned in the bullet points in the "trouble reproducing the bug" section that chromium wasn't affected.
> Using open-source Chromium instead of Chrome did not cause crashes, so we couldn’t see what Chrome code was failing either.
Re: The weirdest bug I've seen yet
#13Discord suffered (suffers?) from a similar thing with gifs. It is or was common for people to post specifically crafted gifs in channels, anyone viewing the channel immediately had their client crash.
Discord client uses Electron, which is in turn Chromium.
Re: The weirdest bug I've seen yet
#14What an interesting conflux of tech to create this bug. That's the web in 2023. I would love to know if it was a Chromium bug that got resolved, but navigating this is tough: https://bugs.chromium.org/p/chromium/issues/list?can=1&q=gif...
Also, I am fully here for Gusto posting this to say "wasn't our fault" and to throw some shade at Grammarly in the process
Re: The weirdest bug I've seen yet
#15> 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.
[deleted]
Re: The weirdest bug I've seen yet
#16If they can figure it out, they're sitting on potentially a very valuable exploit.
Re: The weirdest bug I've seen yet
#17> 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.
haha, that was questionable for me as well. It's ok for Grammarly to read your stuff, but crash metadata is a no no.
Re: The weirdest bug I've seen yet
#18The true bug in the photo is a "candy-striped leafhopper", Graphocephala coccinea, which is tiny but has very striking coloration.
The Larvae of leafhoppers are commonly known as spittlebugs, which create protective bubble nests while feeding on plant stems
Re: The weirdest bug I've seen yet
#19Well, 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.
They nuked my account after trying to charge an expired card three times.
The customer response team was extremely quick and responsive telling me their hands were tied.
Fuck Gusto.
Re: The weirdest bug I've seen yet
#20A disappointing ending to the tale. I really want to know how Grammarly desktop works now. It must have interfered with the Chrome process in some bad way.