Conditional GPU veto analysis |
||||
Issue descriptionI have found no evidence that this is a problem - just making a note. We seem to run the GPU veto analysis regardless of whether GPU rasterization is an option, and for software-only systems this is pure overhead. Is it worth making this step dependent on GPU rasterization availability?
,
May 29 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
,
May 30 2017
Not sure why this was considered a painting bug.
,
Jun 2 2017
I think this is too complicated to conditionally analyze. The analysis is faster now than it used to be (by tracking at record time instead of analyzing the painted content). |
||||
►
Sign in to add a comment |
||||
Comment 1 by chrishtr@chromium.org
, May 27 2016