Implement logging/instrumentation for GPU scheduler |
|||
Issue descriptionDVLOG or similar? Maybe a special command line flag?
,
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.
,
Apr 2 2018
,
May 21 2018
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.
,
Dec 14
|
|||
►
Sign in to add a comment |
|||
Comment 1 by sunn...@chromium.org
, Mar 27 2018