Crash when windows are dragged to edges of extended screen |
||
Issue descriptionGoogle Chrome 54.0.2840.101 (Official Build) (64-bit) Platform 8743.85.0 (Official Build) stable-channel samus Chrome OS Platform: Chromebook Pixel 2 Network info: Office Please specify Cr-* of the system to which this bug/feature applies (add the label below). Steps To Reproduce: (1) Connect external monitor (in this case, Dell U3014t connected via USB-C-HDMI cable) (2) Drag window to any edge of the extended screen Expected Result: Window moved or suggested partitioning of the screen Actual Result: Browser crashes How frequently does this problem reproduce? Always What is the impact to the user, and is there a workaround? If so, what is it? Reopen all tabs Please provide any additional information below. Attach a screen shot or log if possible.
,
Nov 28 2016
Sure, what's the best way to accomplish this? I see this which isn't clear on how to obtain the crash files http://www.chromium.org/chromium-os/packages/crash-reporting/faq#TOC-Where-can-I-find-the-crash-minidump-core-file-for-a-crashed-process-on-my-Chromebook- And this internal site which points to the Chromium page for the relevant FAQ questions. https://sites.google.com/a/google.com/chromeos/resources/engineering/crash-reporting-faq#TOC-Where-can-I-find-the-crash-minidump-core-file-for-a-crashed-process-on-my-Chromebook- - Nik [nfocht]
,
Nov 28 2016
Hello there, You can get crash data by going to chrome://crashes and enabling crash report data. Then, reproduce the error, and you should see the crash page. – brxxn :)
,
Dec 1 2016
Video of issue: https://drive.google.com/open?id=0B9I5lvHLfQBodTZoZW5iVEdMSFk I was trying to show that it wasn't capturing a crash report but it seems it was just a delay. Here are the crash reports: Crash ID: crash/be6da19f00000000 Crash ID: crash/3ae5a19f00000000 Crash ID: crash/b087352300000000 Crash ID: crash/4973a19f00000000
,
Dec 9 2016
I've had a bunch of these this week too. Crash server IDs: a775d45880000000 3c38a36300000000 11f0b6bf00000000 da9ee79880000000 50d2e79880000000 566f679880000000 fa3ce7a300000000
,
Dec 9 2016
I think this is a dup of http://crbug.com/664984, which is allegedly a dup of some other bug I don't have access to.
,
Dec 9 2016
664984 and 643661 are about dual screen setup. - Do you have dual screen and does it still happen on 55 ?
,
Dec 9 2016
I think the root cause seems to be same as 643661 and we should probably dup it to that.
,
Dec 9 2016
> - Do you have dual screen and does it still happen on 55 ? Yes and yes. It seems to crash most frequently when I try to drag from the lower screen to the upper or vice-versa. Last observed on: Version 55.0.2883.82 beta (64-bit) Platform 8872.67.0 (Official Build) beta-channel stumpy Firmware Google_Stumpy.2.102.0 I see that I have an update pending. I'll try installing it and dragging some windows around.
,
Dec 9 2016
Still observable on: Version 55.0.2883.87 beta (64-bit) Platform 8872.70.0 (Official Build) beta-channel stumpy Firmware Google_Stumpy.2.102.0 Crash ID 90077fbf00000000
,
Dec 10 2016
|
||
►
Sign in to add a comment |
||
Comment 1 by brxxnchr...@gmail.com
, Nov 25 2016