blaies, this is the bug tracking your issue. I just tried to repro on a pixel 2 device, and couldn't.
I want to know the exact repro steps, and how you customized your external display. Basically what's in the attached settings page.
Deleted:
Screenshot 2016-10-05 at 11.20.49 - Display 2.png
212 KB
Sure.
I have my main window on external w/ email, and my working tabs (About 6).
My internal has my calendar and hangouts.
I was trying to separate the tabs on my external monitor to have "doc 1" open on top and "doc 2" open on bottom so I could work on both at the same time, but every time I would "pull" the tab away from the main browser window and start to move it, Chrome would crash.
Deleted:
Screenshot 2016-10-05 at 1.24.10 PM.png
26.8 KB
Correct, I was moving it on the same display (Though to be fair, the edges
may have bounced off the side a little bit, therefore simulating me
changing screens?)
Confirm happening on:
Version 55.0.2883.7 dev (64-bit)
Platform 8872.6.0 (Official Build) dev-channel samus
ARC Version 3337798
Firmware Google_Samus.6300.174.0
Feedback sent 08:29 BST
#CBC-RS/TC-watchlist
Just a heads up that this bug is marked as ReleaseBlock-Beta for R55, and we are looking to promote R55 to beta with the build on Monday evening.
Do you think we can get the CL landed in the next day or so and merged to R55 by Monday afternoon?
Since this is a Chrome side CL we should probably try to get this landed by Sunday afternoon so it exists in the Chrome build on Monday.
Looks like it is in the CQ again, though I am afraid we are probably going to miss the first R55 beta with this, since we start a build at 9 and will not have time to PFQ a chrome, we may have to go without it :(.
Does this effectively make external monitor usage impossible? Or is this more like a flake, occasional failure?
Ok thanks, then we will probably just be missing this one for the first beta, but can pick it up in the second (we are running low on time to get a new Chrome into it).
Sorry about the bad merge. I overlooked that crrev.com/6627dfc6e2247fd121673698eef9398c52fcd82d is a dependency of my CL.
Bernie: would it be possible to merge that CL as well, or should I refactor my CL so it applies cleanly on M55?
That is a pretty wide ranging CL, how sure are we that it is safe to merge itself?
Both cherry-picking that CL and modifying your CL carry risk, but it is hard for me to say which is safer, so I would defer to you. If you think we are safer taking the prior CL wholesale then refactoring lets go with that.
Comment 1 by abodenha@chromium.org
, Oct 5 2016Labels: -Pri-2 M-55 ReleaseBlock-Beta Pri-1
Owner: afakhry@chromium.org
Status: Assigned (was: Untriaged)