Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/1f35e553f7c6e49b2a93037dc5a596af173ee7b7 (Remove WebRTC-SystemUDPSendSocketSize study).

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.

This is a serious security regression. If you are not able to fix this quickly, please revert the change that introduced it.

If this doesn't affect a release branch, or has not been properly classified for severity, please update the Security_Impact or Security_Severity labels, and remove the ReleaseBlock label. To disable this altogether, apply ReleaseBlock-NA.

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

The change list identified does not directly have anything to do with the codepath that crashed. The open  Issue 786534  looks quite similar with a different stack and regression range.

gayane: Uh oh! This issue still open and hasn't been updated in the last 14 days. This is a serious vulnerability, and we want to ensure that there's progress. Could you please leave an update with the current status and any potential blockers?

If you're not the right owner for this issue, could you please remove yourself as soon as possible or help us find the right one?

If the issue is fixed or you can't reproduce it, please close the bug. If you've started working on a fix, 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

sergeyu@ I don't think the change is related. Could you also have a look?

I don't have access to the clusterfuzz report. I can't access  crbug.com/786534  either. From what I see here the problem doesn't seem to be related to the change that removed WebRTC experiment.

I cannot access the bug you mentioned either, but I was able to see the clusterfuzz report with my chromium account

Looks like an issue in ash window selector, sammiequon@, can you please take a look.

crash repro steps

1. Open 1 window at least.
2. Enter overview (F5).
3. Press Ctrl+Alt+U.
4. Close all windows.

sammiequon@: Are you actively working on this? It is a security regression, and a stable blocker.

Re #15 https://chromium-review.googlesource.com/c/chromium/src/+/932547 just sent to CQ, that should fix this

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

commit 5e8ca713db9ff36b42f288d5af043a2703449c0a
Author: Sammie Quon <sammiequon@google.com>
Date: Fri Mar 02 22:35:07 2018

overview: Fix crash when exit after using Ctrl Shift U.

We should instead prevent Ctrl Shift U mode in overview somehow, but this
will stop the crash in the meantime.

Test: ash_unittests WindowSelectorTest.ExitInUnderlineMode
Bug:  807517 
Change-Id: Ie7d889937c110583454a281a318b682f62cd6084
Reviewed-on: https://chromium-review.googlesource.com/932547
Reviewed-by: Mitsuru Oshima <oshima@chromium.org>
Commit-Queue: Sammie Quon <sammiequon@chromium.org>
Cr-Commit-Position: refs/heads/master@{#540664}
[modify] https://crrev.com/5e8ca713db9ff36b42f288d5af043a2703449c0a/ash/wm/overview/window_selector.cc
[modify] https://crrev.com/5e8ca713db9ff36b42f288d5af043a2703449c0a/ash/wm/overview/window_selector_unittest.cc

This bug requires manual review: M66 has already been promoted to the beta branch, so this requires manual review
Please contact the milestone owner if you have questions.
Owners: cmasso@(Android), cmasso@(iOS), josafat@(ChromeOS), abdulsyed@(Desktop)

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

+josafat for merge approval

Approved. Branch:3359

Also found by internal fuzzers during the 48 hour window, I'm afraid.

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

commit 36da9721f559a62fc6a02224c168e5b31a639886
Author: Sammie Quon <sammiequon@google.com>
Date: Mon Mar 19 22:12:11 2018

[merge to 66] overview: Fix crash when exit after using Ctrl Shift U.

We should instead prevent Ctrl Shift U mode in overview somehow, but this
will stop the crash in the meantime.

TBR=sammiequon@google.com

(cherry picked from commit 5e8ca713db9ff36b42f288d5af043a2703449c0a)

Test: ash_unittests WindowSelectorTest.ExitInUnderlineMode
Bug:  807517 
Change-Id: Ie7d889937c110583454a281a318b682f62cd6084
Reviewed-on: https://chromium-review.googlesource.com/932547
Reviewed-by: Mitsuru Oshima <oshima@chromium.org>
Commit-Queue: Sammie Quon <sammiequon@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#540664}
Reviewed-on: https://chromium-review.googlesource.com/969641
Reviewed-by: Sammie Quon <sammiequon@chromium.org>
Cr-Commit-Position: refs/branch-heads/3359@{#328}
Cr-Branched-From: 66afc5e5d10127546cc4b98b9117aff588b5e66b-refs/heads/master@{#540276}
[modify] https://crrev.com/36da9721f559a62fc6a02224c168e5b31a639886/ash/wm/overview/window_selector.cc
[modify] https://crrev.com/36da9721f559a62fc6a02224c168e5b31a639886/ash/wm/overview/window_selector_unittest.cc

This bug has been closed for more than 14 weeks. Removing security view restrictions.

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