51–60 of 334 posts
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.
Never do you see the guy investigating memory usage, which is weird.
The 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…
Left me hanging, would not post something like this from my engineering blog. They don't have deeep debugging skills at gusto?
Left me hanging, would not post something like this from my engineering blog. They don't have deeep debugging skills at gusto?
Sounds like they have good time management and prioritisation skills. They found the source of the problem and fixed it.
The main reason for tabs to crash is running out of RAM. Never do you see the guy investigating memory usage, which is weird.
> 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.
For another fun debugging tale, google: Mazda radio Seattle NPR bug
I see some comments highlighting RAM, which could totally have been the issue. Totally looking forward to a follow up to this later down the road, I am sure this isn't going to be the last time we hear of this.