New issue
Advanced search Search tips

Issue 774545 link

Starred by 1 user
Status: WontFix
Owner:
sadrul@chromium.org
Closed: Nov 2017
Cc:
primiano@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

419 KB regression in sizes at 508356:508358

Project Member Reported by primiano@chromium.org, Oct 13 2017 
The only plausible CL in range is

 https://chromium-review.googlesource.com/695724

the other is a one liner fix
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Oct 13 2017 

All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=774545

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=45a0f9dfdb0d4000d0ae3f26f256ba40e001b5a1bc7a2546a2745e6dd4cf6563


Bot(s) for this bug's original alert(s):

win
win-32

Comment 2 by sadrul@chromium.org, Oct 13 2017

Status: Started (was: Assigned)

Comment 3 by sadrul@chromium.org, Nov 9 2017

Status: WontFix (was: Started)
I believe this is expected: parts of the display compositor that used to live in the browser is now included in the gpu process.
►

Sign in to add a comment