Issue metadata
Sign in to add a comment
|
Regression : On Launching Chrome Weird behavior is seen |
||||||||||||||||||||||
Issue descriptionChrome Version: 64.0.3241.0/10038.0.0 dev-channel Kip,Reks and Peppy OS: Chrome What steps will reproduce the problem? (1)Sign into User -> Launch Chrome -> Now observe wallpaper background is seen (2)Open any Page (Ex; chrome://settings)-> now again open New tab and observe settings page traces is seen and also weird flickering seen (Please refer Video) Expected: No such Weird behavior is seen Actual: Instead Weird behavior is seen This is Regression issue as same is working fine in 63.0.3236.0/10024.0.0 dev-channel Reks
,
Oct 16 2017
I am no longer actively working on the Chromium project.
,
Oct 17 2017
@tbuckley : Please confirm the Issue
,
Oct 24 2017
Hi all, We may attempt a M64 DEV release as soon as this Thursday (though next week is more likely). This bug will block us from proceeding. This one has been open / unconfirmed for a while. Can we confirm impact, boards affected, and true blocking status? Thanks bunches.
,
Oct 24 2017
@mmanchala, this is unrelated to any of my projects. Please find a more general owner or use components to help find one. @marcheu does this look like a CrOS graphics issue? It's affecting both the WebUI of the New Tab Page as well as the omnibox, so it's not specific to Blink.
,
Oct 24 2017
@5: this looks like compositor, CCing people who might have seen it/might know.
,
Oct 24 2017
It might be partial swap or raster problem, can the original poster bisect to a CL?
,
Oct 24 2017
@mmanchala can you run a bisect? If not please assign back to danakj@
,
Oct 25 2017
C#8 > Bisect setup is not available for ChromeOS to narrow it down. Issue seems to be fixed on latest ToT build 64.0.3246.0/10062.0.0 dev-channel Candy,Daisy,Reks and Peppy Thanks..!!
,
Oct 26 2017
If fixed can we remove the M64 Dev Blocker, or more verification required? Thanks
,
Oct 30 2017
Pri-0 bugs are critical regressions or serious emergencies, and this bug has not been updated in three days. Could you please provide an update, or adjust the priority to a more appropriate level if applicable? If a fix is in active development, please set the status to Started. Thanks for your time! To disable nags, add the Disable-Nags label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 31 2017
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by mmanchala@chromium.org
, Oct 16 2017Status: Assigned (was: Untriaged)