Improve handling of component extension crashiness |
||||
Issue descriptionVarious things can cause extension processes to crash. For normal extensions, the user gets a pop-up informing them of the crash and prompting them to click to re-launch the extension. For component extensions we don't prompt; we just wait 3s and re-launch. This works well for transient crashers but is less obviously correct for pathological crashers. Simply throttling re-launch risks masking the issue; ideally we want to detect pathological component crashes and prompt the user to let them know that things are broken, perhaps file a feedback report, etc.
,
Aug 19 2016
Marking as available to get this bug out of triage queue - Devlin can probably figure out where to prioritize this.
,
Aug 26 2016
,
Aug 28 2017
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
||||
►
Sign in to add a comment |
||||
Comment 1 by w...@chromium.org
, Aug 18 2016