Using the per-revision bisect providing the bisect results,
Good build: 55.0.2879.0 (Revision: 422347)
Bad build: 55.0.2880.0 (Revision: 422654)

You are probably looking for a change made after 422588 (known good), but no later than 422589 (first known bad).

CHANGE-LOG URL:
---------------------------------------
https://chromium.googlesource.com/chromium/src/+log/745fe06919e14e926d3464f64bc2f0d91b00b326..fd7bb627894ab5fc1415c90f579dba779fddc70f


From the CL above, assigning the issue to the concern owner

@rdevlin.cronin: 
------------------
Could you please look into the issue, pardon me if it has nothing to do with your changes and if possible please assign it to concern owner.

Review-Url:  https://codereview.chromium.org/2386823002

Note: Able to reproduce the issue on Mac 10.12.2,Ubuntu 14.04 & Win7.

I don't think https://codereview.chromium.org/2386823002 would have caused this.  Can we get another bisect?

Using the per-revision bisect providing the bisect results,
Good build: 55.0.2879.0 (Revision: 422347)
Bad build: 55.0.2880.0 (Revision: 422654)


After executing the bisect(old) script , i got the following CL's between good and bad build versions
===========================================
https://chromium.googlesource.com/chromium/src/+log/99c2073218960208c0f54de95b9c31ff9521ba46..a525387e44b256f162626c25fa14dd199d9c4094

The suspecting Change Log is :
-----------
https://chromium.googlesource.com/chromium/src/+/a525387e44b256f162626c25fa14dd199d9c4094

From the above CL suspecting the below change
---------------------------
Review-Url: https://codereview.chromium.org/2391763003

michaelpg@- Could you please look into this issue, if it's related to your change?  if not could you please help us to reassign this issue to the right owner.

Sorry for the typo mistake, for this issue, per-revision bisect script was executed. 

Themes don't even have permissions (I checked that specific CRX). Unless there's something weird happening in the manifest_features generator (devlin?) I don't think my change seems likely either.

From the white full-screen flicker when the reset button is hit in the "Actual" video, and the weirdness of the Incognito window afterwards, I wonder if this is some kind of graphics glitch. Getting two different bisect results is suspicious too.

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

Can't reproduce this anymore. I suspect that it might have been fixed with the changes in the code around background colors that treib@ has been working on.

Please reopen if this still can be reproduced under some circumstances.