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

Issue 781247 link

Starred by 2 users

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Task

Blocking:
issue 730193



Sign in to add a comment

Measure browser crash rate improvement with --enable-viz

Project Member Reported by kylec...@chromium.org, Nov 3 2017

Issue description

Turning on --enable-viz moves a large/complex piece of code from the browser to GPU process. Any bugs in this code that cause browser crashes will instead cause GPU crashes. GPU crashes are recoverable and the user experience should be better. We should do some measurements to get an idea on the potential improvement here.

1. We can look at crash reports for the browser process that originate in specific source files that are only used in the display compositor. These crashes would presumably happen in the GPU process instead of the browser process. This gives us an upper bound on the number of crashes we make recoverable.
2. When we are confident enough that --enable-viz works for a finch trial (presumably on Windows or Chrome OS) we can compare browser crash rate directly. This will give us a much better idea of the potential improvement.
 

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

Components: -Internals>Viz Internals>Services>Viz
Migrating from Internals>Viz to Internals>Services>Viz.
Blocking: -601863 732572
Blocking: -732572 787097
Components: -Internals
Blocking: -787097 730193

Sign in to add a comment