Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

The weirdest bug I've seen yet

engineering.gusto.com

Post reply on HN
Print view View original

21–30 of 334 posts

Re: The weirdest bug I've seen yet

#21

Post by j1mmie »

flutas wrote: post #12
madeofpalk wrote: post #10

> 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.

I wonder what version of Chromium they used. If it was a nightly, it could be weeks before the fix makes it into Chrome. They might've tested at a time when latest Chrome had the bug and Chromium didn't.

Re: The weirdest bug I've seen yet

#23

Post by hyperhello »

yuck39 wrote: post #3
wobblyasp wrote: post #2

Such 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?

I would guess the gif triggers a specific edge case that would crash, and grammarly is just a common enough addition to chrome with a lot of edge case triggers that it was identified. I’d guess this is on the Chrome team to fix soon, but yeah, at least post the spinner file for us!

Re: The weirdest bug I've seen yet

#24

Post by [deleted] »

Modified3019 wrote: post #18

The 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

[deleted]

Re: The weirdest bug I've seen yet

#25

Post by Kognito »

Andrex wrote: post #19
0xNotMyAccount wrote: post #7

Earlier quoted context omitted.

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.

Hate that.

“Sorry, the system says no”

Had similar situations with PayPal and Uber recently where their support have absolutely no information or ability to take a decision.

Support essentially becomes a glorified text-to-speech system.

Re: The weirdest bug I've seen yet

#26

Post by [deleted] »

Andrex wrote: post #19
0xNotMyAccount wrote: post #7

Earlier quoted context omitted.

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.

[deleted]

Re: The weirdest bug I've seen yet

#27

Post by orbv »

flutas wrote: post #12
madeofpalk wrote: post #10

> 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.

Google provides symbols for Chrome release builds, including source indexing so source code should be available. See sections symbol server and source indexing at https://www.chromium.org/developers/how-tos/debugging-on-win...

Re: The weirdest bug I've seen yet

#30

Post by JohnMakin »

roozbeh18 wrote: post #17
dblitt wrote: post #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.

haha, that was questionable for me as well. It's ok for Grammarly to read your stuff, but crash metadata is a no no.

Welcome to security in 2023 :)
Post reply on HN