The weirdest bug I've seen yet

Post by mplewis » Thu, Nov 30, 2023, 8:47 PM UTC

lobf wrote: post #96

neilv wrote: post #63

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

You must not have read the article because he literally addresses this.

Post by MattDaEskimo » Thu, Nov 30, 2023, 8:50 PM UTC

AnimalMuppet wrote: post #61

tedivm wrote: post #47

Earlier quoted context omitted.

Was it actually a Chrome bug though? It only happened when the Grammerly desktop app was installed. My guess is grammerly is doing something sketchy.

Does Grammerly hook something in Chrome? If not, then it's still probably a Chrome bug, even if some second-order effect of Grammerly is necessary to trigger it.

Post by MattDaEskimo » Thu, Nov 30, 2023, 8:52 PM UTC

kube-system wrote: post #85

neilv wrote: post #63

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

> They don't address why they didn't just run Chromium. Or Firefox. Probably: 1. Because it is reasonable to expect the application to work in Chrome. 2. Chromium isn't intended for production use cases. Back when IE and Chrome had about equal market share, I worked somewhere that had one team insisting that all employees must use IE for one of their applications, and another team insisting that all employees use Chr…

Post by whimsicalpedal » Thu, Nov 30, 2023, 8:54 PM UTC

marcellus23 wrote: post #57

mgaunard wrote: post #52

The main reason for tabs to crash is running out of RAM. Never do you see the guy investigating memory usage, which is weird.

Yeah, that would have been a good first step, but he does admit to not really knowing much about browsers: > This was fairly far outside the usual scope of our on-call issues. Our team is generally well-insulated by other teams from issues like browser compatibility, so I didn’t know the first thing about browser debugging.

Post by ryandrake » Thu, Nov 30, 2023, 8:55 PM UTC

_jal wrote: post #103

ecshafer wrote: post #87

I don't think I would believe myself if I found this being a specific gif. This is a great amount of coincidences in code to cause this. Grammarly is an application that I don't get. The fact that people are installing, basically spyware, on their computers just to get grammar suggestions to make their writing more boring and add a spellchecker (which is already inside web browsers) is pretty astounding to me. The fa…

> Grammarly is an application that I don't get. You write like a native speaker, so I'm not surprised. But imagine having a few years of school-German, and then taking a German language job. I'd bet there would be times you'd want a writing assistant, too. There are also plenty of native English speakers who for whatever reason got a crappy education, and didn't get a lot of writing feedback. As far as corporate secu…