Extremely disappointing that they seem to have neither investigated nor enabled others to investigate (e.g. by filing a bug against Chrome).
This smells like a potential security vulnerability.
The weirdest bug I've seen yet
71–80 of 334 posts
Re: The weirdest bug I've seen yet
#72> Using open-source Chromium instead of Chrome did not cause crashes, so we couldn’t see what Chrome code was failing either. They don't address why they didn't just run Chromium. Or Firefox. (This is potentially better than the 'solution' they much later ended up with, in which they probably only relieved a symptom of an underlying problem that can exhibit again, and in the meantime is a zero-day exploit waiting to…
What makes this doubly frustrating is that they also didn't report the bug to Chrome. It's super easy to do, plus they're very responsive if you have a repro case which in this case they do. I think I'm now up to three or four Chrome bugs reported that their team has subsequently fixed.
Re: The weirdest bug I've seen yet
#73The weirdest one I saw was this: User claims that the wording of the info they enter into a certain form changes when they save. At first I suspected someone else editing the same form at the same time unbeknownst to each other but it wasn't the case according to the logs. And I saw the correct wording on my own computer. Then I noticed in their screenshots that some of the menus had weird wording too. Turns out they…
I added
Apparently the new incantation to fix an app (can be applied to an element) is (ugly: I presume it isn't CSS to avoid supporting dynamically changing it):
Every now and then I would look at the meta tags for a major single page app and discover some new horror when searching for the reason for the meta tag!
Re: The weirdest bug I've seen yet
#74I have a saying that isn't perfectly true but often will apply to "fixes" like this - If you don't know why the fix worked, you may not have actually fixed it.
But you may have
Re: The weirdest bug I've seen yet
#75Reminds 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
Re: The weirdest bug I've seen yet
#76[deleted]
Re: The weirdest bug I've seen yet
#77I'm guessing this is the webp bug.
The auto conversion to webp on the backend, signaled by chrome, resulted in a bad image that crashes the browser due to grammarly parsing of said bad webp.
Safari doesn't tell the server it does webp and so it downloads the actual gif, and doesn't crash.
Re: The weirdest bug I've seen yet
#78I have a saying that isn't perfectly true but often will apply to "fixes" like this - If you don't know why the fix worked, you may not have actually fixed it.
But they couldn't fix the bug: The bug was in another product that they couldn't access source code or submit patches.
The best they could do was work around it.
Sometimes workarounds are the best you can do until your vendor provides a real fix.
Re: The weirdest bug I've seen yet
#79> Using open-source Chromium instead of Chrome did not cause crashes, so we couldn’t see what Chrome code was failing either. They don't address why they didn't just run Chromium. Or Firefox. (This is potentially better than the 'solution' they much later ended up with, in which they probably only relieved a symptom of an underlying problem that can exhibit again, and in the meantime is a zero-day exploit waiting to…
What makes this doubly frustrating is that they also didn't report the bug to Chrome. It's super easy to do, plus they're very responsive if you have a repro case which in this case they do. I think I'm now up to three or four Chrome bugs reported that their team has subsequently fixed.
They said it wasn't reproducible anymore though. So if they make a bug report now and say "this used to cause a crash in an old version of Chrome while also having an old version of another software installed, but is no longer reproducible in latest builds", most people would probably just ignore it.