[meta] Need a process to deal with bugs filed from crash server (that are typically unactionable) |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue descriptionThe style team receives an estimated 4-5 filed crash bugs each week. Historically, we have not managed to fix (as in verifiably stop the reporting of crashes) a single crash bug that was reported solely on the crash server. Note that this doesn’t mean that crashes persist forever - they don’t. What it means is that any time we’ve spent on these bugs has been time that was wasted. The amount of time we’ve spent has been significant. For example, crash bugs have been part of our daily and weekly bug processes for 2 years now. Additionally we have had individual engineers look at crash bug instances for days to weeks at a time. Finally, as a team, we recently dedicated a full week to understanding and attempting to fix crash bugs. Something’s going wrong. Rather than continue to throw good time after bad, we’ve decided to suspend processing of these bugs until we have a process in place for dealing with them. Stay tuned.
,
Mar 29 2017
I’ve scheduled a meeting for us in April to speak with someone from the crash server team. Hopefully that will give us a better handle on how to deal with these bugs.
,
Mar 29 2017
,
Apr 11 2017
,
Apr 19 2017
The proposed meeting will happen next week.
,
Apr 20 2017
,
Apr 26 2017
,
May 2 2017
,
May 9 2017
,
May 10 2017
,
May 15 2017
Has there been any progress on this issue after talking with the crash server team?
,
May 15 2017
,
May 23 2017
,
May 23 2017
Yes, sorry for the lack of updates. An outcome of the meeting was that it was asked of the crash team that it be easier to tell if the crash was present in a build that was going to be promoted to the next channel (eg beta_>stable). We still don't have a nice simple threshold for what is a crash that should be paid special attention to. And we don't have a good answer to the difficulty of being able to repro a crash from the crash server.
,
May 31 2017
,
May 31 2017
,
May 31 2017
,
May 31 2017
,
Jun 1 2017
Users experienced this crash on the following builds: Win Dev 60.0.3112.7 - 0.36 CPM, 29 reports, 28 clients (signature [Renderer hang] blink::ElementRuleCollector::CollectMatchingRules) If this update was incorrect, please add "Fracas-Wrong" label to prevent future updates. - Go/Fracas
,
Jun 2 2017
Users experienced this crash on the following builds: Win Beta 59.0.3071.82 - 0.29 CPM, 46 reports, 46 clients (signature [Renderer hang] blink::ElementRuleCollector::CollectMatchingRules) If this update was incorrect, please add "Fracas-Wrong" label to prevent future updates. - Go/Fracas
,
Jun 3 2017
Users experienced this crash on the following builds: Win Canary 61.0.3117.0 - 0.25 CPM, 11 reports, 11 clients (signature [Renderer hang] blink::ElementRuleCollector::CollectMatchingRules) If this update was incorrect, please add "Fracas-Wrong" label to prevent future updates. - Go/Fracas
,
Jun 4 2017
Adding fracas-wrong label, as this bug is blocking the crash bugs. It looks like a bug in Fracas that this happens - each update doesn't contain any information about *which* crash it's referring to.
,
Jun 6 2017
,
Jun 7 2017
,
Jun 7 2017
,
Jun 7 2017
,
Jun 7 2017
,
Jun 8 2017
,
Jun 13 2017
,
Jun 14 2017
,
Jun 14 2017
,
Jun 14 2017
,
Jun 14 2017
,
Jun 16 2017
,
Jun 19 2017
,
Jun 19 2017
,
Jun 21 2017
,
Jun 21 2017
,
Jun 22 2017
,
Jun 22 2017
,
Jun 22 2017
,
Jul 2 2017
,
Jul 2 2017
,
Jul 4 2017
,
Jul 12 2017
,
Jul 16 2017
,
Jul 19 2017
,
Jul 27 2017
,
Aug 7 2017
,
Aug 17 2017
,
Aug 29 2017
,
Aug 29 2017
,
Sep 25 2017
,
Sep 25 2017
,
Oct 3 2017
,
Oct 3 2017
,
Oct 4 2017
,
Nov 7 2017
,
Nov 27 2017
,
Nov 30 2017
,
Dec 6 2017
,
Dec 11 2017
,
Jan 4 2018
,
Jan 23 2018
,
Feb 2 2018
Hi Mike, Are you happy to keep owning this bug or would you like to change owners to someone on the Layout team?
,
Feb 2 2018
That's a good point Naina. I'll sync with the Layout team next week and come up with A New Plan.
,
Feb 16 2018
,
May 24 2018
,
Jul 3
,
Aug 29
,
Oct 26
,
Oct 26
,
Nov 22
,
Nov 23
,
Nov 23
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Comment 1 by dstockwell@chromium.org
, Mar 29 2017