New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 780970 link

Starred by 1 user
Status: WontFix
Owner:
█ chongz@chromium.org
Last visit > 30 days ago
Closed: Oct 3
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug
Proj-Servicification

Blocking:
issue 737282



Sign in to add a comment

Network Service: Crash the browser after n restarts

Project Member Reported by chongz@chromium.org, Nov 2 2017 
In most cases users should be able to click the link again or refresh the page to get things working again. However we could make it better by:
1. Silently retry failed network request.
2. Send a popup if things went wrong.
3. Run NS in browser if it keeps crashing.

More could be added but this shouldn't be a blocking bug.

Comment 1 by laforge@google.com, Nov 7 2017

Components: -Internals>Network>Service Internals>Services>Network
Apologies, applied the wrong component in bulk.

Comment 2 by chongz@chromium.org, May 9 2018

Summary: Network Service: Crash the browser after n restarts (was: Make NS crash handling more user friendly)
As discussed in the Error Handling doc[1] we don't want to disturb users or run NS in browser, and 1. is orthogonal to the crash handling effort.

A reasonable approach is to gather metrics and crash the browser after n restarts.

[1] https://docs.google.com/document/d/1CZMPzQrmGvjz3O7RC-MR56fStLJj1RjdKNkFItzJs0Y/edit?usp=sharing#heading=h.v0mmyacvapyd

Comment 3 by chongz@chromium.org, May 18 2018 

This bug will not block canary

Comment 4 by dxie@chromium.org, May 22 2018

Labels: Hotlist-KnownIssue

Comment 5 by jam@chromium.org, Oct 3

Status: WontFix (was: Assigned)
►

Sign in to add a comment