Thought this was going to be about Gusto "remember this device" which keeps failing. Reported like 2 years ago
The weirdest bug I've seen yet
31–40 of 334 posts
Re: The weirdest bug I've seen yet
#32> 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
#33Well, 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.
Maybe it’s because Grammarly enables full accessibility support in Chrome to be able to access all elements in the browser (similar to a screen reader). This has caused me various issues in the past (e.g. https://bugs.chromium.org/p/chromium/issues/detail?id=136448... ). However it’s probably good that the Accessibility functions get more exposure due to this.
Re: The weirdest bug I've seen yet
#34Such a tease. At least upload the gif so people can poke at it!
[deleted]
Re: The weirdest bug I've seen yet
#35Well, 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.
That's unfair: isn't this is exactly how most strange bugs get "fixed" by most companies?
It is an abnormal developer and an even more abnormal business that actually spends enough time to find the root cause of outré glitches. Especially when you start having to debug complex third party systems to debug them properly - requires skills and motivation plus a company that will encourage a developer to do that.
The story is not specific to Gusto - it is the story of every developers life. I have chased down bugs in my OS and my browser - it is rarely well rewarded! Fixing a compiler bug should be on my bucket list! A long time ago I worked around a compiler bug by inserting a label: (I think the label prevented certain optimisations where the label was put).
Re: The weirdest bug I've seen yet
#36Thought this was going to be about Gusto "remember this device" which keeps failing. Reported like 2 years ago
[deleted]
Re: The weirdest bug I've seen yet
#37A 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.
[deleted]
Re: The weirdest bug I've seen yet
#38Twirly prompts have sucked, for weird reasons, since the WWIV BBS days.
I guess some things never change.
Re: The weirdest bug I've seen yet
#39I 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.
This sounds more like a hardware fault than something wrong with the software, especially since it doesn't seem to be deterministic.
But stranger things have happened, and given the enormous surface area of a modern computer (hardware, software, drivers, state, etc.) can anything truly be deterministic?
Re: The weirdest bug I've seen yet
#40Well, 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.
The GIF cannot be responsible: as untrusted web content, if it can trigger a crash, the responsibility lies with the local software stack. So you have only two suspects: Chrome and Grammarly. The GIF is at most an accomplice.