New issue
Advanced search Search tips

Issue 826543 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug

Blocked on:
issue 797137

Blocking:
issue 828157



Sign in to add a comment

Implement logging/instrumentation for GPU scheduler

Project Member Reported by sunn...@chromium.org, Mar 27 2018

Issue description

DVLOG or similar? Maybe a special command line flag?
 
Blockedon: 797137

Comment 2 by piman@chromium.org, Mar 28 2018

Is this something we could have in production (maybe behind a flag, VLOG may be good enough)?
It could be interesting also to see if we can have a way to dump scheduler state, e.g. via a hot key (if a user has a browser that seems stuck), or programmatically when the browser (or renderer?) detects a hang.
Blocking: 828157
Bulk edit**

This bug has the label Postmortem-Followup but has not been updated in 3+ weeks. We are working on a new workflow to improve postmortem followthrough. Postmortems and postmortem bugs are very important in making sure we don't repeat prior mistakes and for making Chrome better for all.

We will be taking a closer look at these bugs in the coming weeks. Please take some time to work on this, reassign, or close if the issue has been fixed. Thank you.
Labels: -Pri-1 Pri-2

Sign in to add a comment