Narrowing down to between 9995 (good) and 10000 (bad).

actually, 9995 seems to be very unstable I can't really tell what's going on.

I think I got it down to 9995 is bad and 9989 is good.

R63-9991.0.0 is the first bad, R63-9990.0.0 is the last good.

I believe the changes are:

https://chromium.googlesource.com/chromium/src/+log/63.0.3223.0..63.0.3228.0?pretty=fuller&n=10000
https://crosland.corp.google.com/log/9990.0.0..9991.0.0

There's little Chrome OS changes but unfortunately it's a large chrome uprev jump.

reproduced on bob 64 10041.0.0 too, but kevin and bob are very similar.

bisected chrome, and this seems to be the CL that caused the problem.


commit 115ac3528d0a279b55f5ec5ae82a872db9da3911 (HEAD)
Author: Mitsuru Oshima <oshima@chromium.org>
Date:   Wed Sep 27 03:21:33 2017 +0000

    Generate DispayInfo for disconnected internal display
    
    DisplayManager knows if the device has internal display, but
    didn't populate the ManagedDisplayInfo if it's not connected
    already.
    
     logout in doced mode. The scale used for ARC++ should be correct.
    
    Bug: 66227368
    Test: Covered by unit tests. Also tested on device.
    Change-Id: Ifdf2b0d00b63d3aeef008882ca1e01a500cb9a9d
    Reviewed-on: https://chromium-review.googlesource.com/683233
    Reviewed-by: Ahmed Fakhry <afakhry@chromium.org>
    Commit-Queue: Mitsuru Oshima <oshima@chromium.org>
    Cr-Commit-Position: refs/heads/master@{#504571}

hmm.. I see this change was cherry-picked to M62. Does M62 work with this patched in? 
b/66227368

Adding some tags.

This issue is marked as a release blocker with no OS labels associated. Please add an appropriate OS label.

All release blocking issues should have OS labels associated to it, so that the issue can tracked and promptly verified, once it gets fixed.

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

Please add appropriate OSs.

kylechar@, I noticed that the native bounds of the internal display changes when external display is connected on kevin (but not on carioline)

[0, 0, 2400x1600] single 
to
[0, 1260 2400x1600] dual

Is this expected?

Does this actually happen on 62?

And does this happen only on RK3399 systems?

External display is working fine for me on a samus running 10001...

The CL is already in the current live beta, so we have no reason to block 62 beta based on this, another update will not make it worse, but if this is happening we need it fixed before stable, if we don't have a fix by tomorrow afternoon we should revert the CL.

Is this different than  bug #774668 ?

 Issue 774668  has been merged into this issue.

The symptom in #12 seems to be board specific, and can happen in 62.
CL is under review now: https://chromium-review.googlesource.com/c/chromium/src/+/726262

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/ca1309e1130def3f01b093f53e083258ea214e78

commit ca1309e1130def3f01b093f53e083258ea214e78
Author: Mitsuru Oshima <oshima@chromium.org>
Date: Thu Oct 19 22:10:07 2017

Do not re-register dislay info if exists

UpdateInternalDisplay should register the display info
only if
1) no internal display info  is registered. (it'll be
  treated as new display)
2) it's disconnected

BUG= 774383 
TEST=covered by unit test. manually tested on kevin.

Change-Id: Ifdf74ad7e61a0d5ffa617e0a72622e2ddb9bbebd
Reviewed-on: https://chromium-review.googlesource.com/726262
Commit-Queue: Mitsuru Oshima <oshima@chromium.org>
Reviewed-by: Ahmed Fakhry <afakhry@chromium.org>
Cr-Commit-Position: refs/heads/master@{#510235}
[modify] https://crrev.com/ca1309e1130def3f01b093f53e083258ea214e78/ash/display/display_manager_unittest.cc
[modify] https://crrev.com/ca1309e1130def3f01b093f53e083258ea214e78/ui/display/manager/chromeos/display_change_observer.cc

This bug requires manual review: Request affecting a post-stable build
Please contact the milestone owner if you have questions.
Owners: amineer@(Android), cmasso@(iOS), bhthompson@(ChromeOS), abdulsyed@(Desktop)

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/68052a3094af829b1b5f0dafcc3d63e488184f2c

commit 68052a3094af829b1b5f0dafcc3d63e488184f2c
Author: Mitsuru Oshima <oshima@chromium.org>
Date: Mon Oct 23 19:26:53 2017

Do not re-register dislay info if exists

UpdateInternalDisplay should register the display info
only if
1) no internal display info  is registered. (it'll be
  treated as new display)
2) it's disconnected

BUG= 774383 
TEST=covered by unit test. manually tested on kevin.

(cherry picked from commit ca1309e1130def3f01b093f53e083258ea214e78)

Change-Id: Ifdf74ad7e61a0d5ffa617e0a72622e2ddb9bbebd
Reviewed-on: https://chromium-review.googlesource.com/726262
Commit-Queue: Mitsuru Oshima <oshima@chromium.org>
Reviewed-by: Ahmed Fakhry <afakhry@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#510235}
Reviewed-on: https://chromium-review.googlesource.com/733941
Reviewed-by: Mitsuru Oshima <oshima@chromium.org>
Cr-Commit-Position: refs/branch-heads/3202@{#727}
Cr-Branched-From: fa6a5d87adff761bc16afc5498c3f5944c1daa68-refs/heads/master@{#499098}
[modify] https://crrev.com/68052a3094af829b1b5f0dafcc3d63e488184f2c/ash/display/display_manager_unittest.cc
[modify] https://crrev.com/68052a3094af829b1b5f0dafcc3d63e488184f2c/ui/display/manager/chromeos/display_change_observer.cc

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/ffc81e408f4eef98554553f0496768854a5ab42e

commit ffc81e408f4eef98554553f0496768854a5ab42e
Author: Mitsuru Oshima <oshima@chromium.org>
Date: Mon Oct 23 19:28:44 2017

Do not re-register dislay info if exists

UpdateInternalDisplay should register the display info
only if
1) no internal display info  is registered. (it'll be
  treated as new display)
2) it's disconnected

BUG= 774383 
TEST=covered by unit test. manually tested on kevin.

Change-Id: Ifdf74ad7e61a0d5ffa617e0a72622e2ddb9bbebd
Reviewed-on: https://chromium-review.googlesource.com/726262
Commit-Queue: Mitsuru Oshima <oshima@chromium.org>
Reviewed-by: Ahmed Fakhry <afakhry@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#510235}(cherry picked from commit ca1309e1130def3f01b093f53e083258ea214e78)
Reviewed-on: https://chromium-review.googlesource.com/734123
Reviewed-by: Mitsuru Oshima <oshima@chromium.org>
Cr-Commit-Position: refs/branch-heads/3239@{#160}
Cr-Branched-From: adb61db19020ed8ecee5e91b1a0ea4c924ae2988-refs/heads/master@{#508578}
[modify] https://crrev.com/ffc81e408f4eef98554553f0496768854a5ab42e/ash/display/display_manager_unittest.cc
[modify] https://crrev.com/ffc81e408f4eef98554553f0496768854a5ab42e/ui/display/manager/chromeos/display_change_observer.cc