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

271–280 of 334 posts

Re: The weirdest bug I've seen yet

#271

Post by sodality2 »

nightfly wrote: post #215
aquafox wrote: post #160

I randomly had the issue that after booting up Linux, I didn't have any sound. Turns out it was related to my Windows dual-boot setup! When restarting from Windows, Windows doesn't shut down my realtek audio device, but only puts it to sleep and Linux fails to start it. Only solution is to always do a shutdown from Windows and then hitting the power button. The issue is still there: https://askubuntu.com/questions/10…

I've seen the opposite-ish: Someone who was dual booting windows and linux only had working wifi if they booted into windows and rebooted into linux. The linux install didn't have the firmware package for their wifi card installed, so when rebooting from windows into linux it was still all primed and ready to go but not when cold booting into linux directly.

This is my exact problem with a HP envy X360. HP refuses to fix the bug in BIOS. :/

https://bugzilla.redhat.com/show_bug.cgi?id=2107845

Re: The weirdest bug I've seen yet

#272

Post by suzzer99 »

superfrank wrote: post #75
user3939382 wrote: post #46

Reminds me of the story I read where the guy's car wouldn't start depending on what flavor of ice cream he picked and when investigated he was right. Some kind of evaporation/vacuum leak or something that was dependent on time and some flavors were farther away in the store and took more time to buy.

Up there with the "I can't send an email over 500 miles" story https://web.mit.edu/jemorris/humor/500-miles

I love this one so much.

Re: The weirdest bug I've seen yet

#274

Post by hirsin »

noizejoy wrote: post #243
OsrsNeedsf2P wrote: post #180

Earlier quoted context omitted.

As an engineer, yes Firefox is a good solution As a PM, we spent 4 months making the onboard easier, and now you want people to install a new browser?

Having multiple browsers as a standard installation and employee training is an investment in business continuity. And business continuity investment is like insurance: A waste until you need it. Too much monoculture is short sighted and long term expensive.

Do you ship them extra computers too? Dual boot? There's gotta be a limit somewhere, and browser choice is a fair one.

For engineers, absolutely, two browsers because some are liable to hit (self or team induced) bugs. But for sales? Support? Nah.

Re: The weirdest bug I've seen yet

#275

Post by jsunderland323 »

karmakaze wrote: post #237
gelatocar wrote: post #152

As I was reading this I was thinking to myself "I wonder if it is grammarly related" because I experienced a bug some time ago that presented itself in a similar way. It was impossible to reproduce but affecting lots of people internally within certain departments. Eventually we figured out the thing they had in common was that they had the Grammarly extension installed. The other key thing was that the bug only appe…

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.

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

#276

Post by langsoul-com »

sfink wrote: post #167

Next time this happens, I recommend just letting people use a different browser. Firefox in particular has gotten much better at importing bookmarks, passwords, etc. from Chrome. It was a Sign from the universe that it was time to make the switch. Who are we to reject Signs? (Full disclosure: I'm an engineer on Firefox. But that has nothing whatsoever to do with my advice here, no siree Bob, not in the least.)

Chrome is over half the market. Not a good sign for a browser based product to not properly work on the most used browser on the world...

Re: The weirdest bug I've seen yet

#277

Post by robocat »

resonious wrote: post #236

I gotta say, the ending was pretty disappointing. I was so hyped to learn why Grammarly crashes when Chrome loads a particular gif. What about the gif was different? What part of Grammarly made that happen? I hate to say it but this is modern web dev in a nutshell. Remove stuff until you find where the bug is, tweak it randomly until it's fixed, done. No root cause analysis or anything deep. This is a great post anyw…

> No root cause analysis or anything deep.

Spending time to create a test case and sending it to the browser bug team gets the bug fixed? Riiiiiiiiight.

Actually I did that for a while and the Chromium team would occasionally fix some fairly subtle issues: assuming I could make a demo of the problem and took the time to write up a good bug report. Maybe they just liked me! The Chromium team also wrote fantastic public followup to bug reports (whether fixed or not).

Certainly I never had any luck getting even extremely serious browser bugs fixed by anyone else (Apple, Mozilla, Microsoft) regardless of how much time I wasted trying to give good informative bug reports. And you never found out anything further - talking to walls is more productive.

It feels good trying to help the world be a better place, but it wasn't worth it.

Don't waste your time fighting windmills. Find a workaround, document it with a comment, forget about it. Do something that makes your business successful instead.

Re: The weirdest bug I've seen yet

#278

Post by jolux »

karmakaze wrote: post #237
gelatocar wrote: post #152

As I was reading this I was thinking to myself "I wonder if it is grammarly related" because I experienced a bug some time ago that presented itself in a similar way. It was impossible to reproduce but affecting lots of people internally within certain departments. Eventually we figured out the thing they had in common was that they had the Grammarly extension installed. The other key thing was that the bug only appe…

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.

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

#279

Post by rhaps0dy »

jolux wrote: post #278
karmakaze wrote: post #237

Earlier quoted context omitted.

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.

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.

If you read carefully you will see that they said the bug didn’t replicate with Chromium
Post reply on HN