Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.

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

Could be related to your recent changes.

0b61507	by	aleventhal@chromium.org	
on 2018-05-17 14:25 (local)
ARIA tables using table CSS incompletely have bad AX structure
3f72dc8	by	aleventhal@chromium.org	
on 2018-05-16 15:28 (local)
Any ARIA attribute should cause a node to be exposed
a3f82b7	by	aleventhal@chromium.org	
on 2018-05-16 12:13 (local)
Aria details should force spans to be exposed

 Issue 825769  has been merged into this issue.

aleventhal: 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

Friendly ping. :) We need to get fixes for High severity vulnerabilities shipped to users in 60 days (see https://chromium.googlesource.com/chromium/src/+/master/docs/security/severity-guidelines.md#High-severity).

Also, does this code run on Android, Chrome OS, and/or Fuchsia? Please check the boxes if so. Thanks!

aleventhal: Uh oh! This issue still open and hasn't been updated in the last 34 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

Hey Dominic, hate to do this to you, but this seems accessibility-related and aleventhal hasn't been responsive, so do you think you could find an appropriate owner for this one?  Thanks heaps! 

I've got it, apologies for overlooking it.

I have created a layout test from this that crashes as far back as November 29, 2017. I'm having trouble finding a version where it doesn't crash, because if I go back far enough, the layout tests complain about dependencies and don't run. If someone experienced wants to help with that, it might be helpful.

Either this never worked or regressed a long time before the CL's in comment 6 were landed. Those don't make sense for regressing this anyway, as there are no tables or ARIA in the testcase.

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

commit e0b51b89bac38a15c9e48eba313673b0b32f471f
Author: Aaron Leventhal <aleventhal@chromium.org>
Date: Tue Jul 03 03:18:03 2018

Guard against |this| being deleted in test script

The layout bugs test runner uses an altered code path to post a11y
notifications, that allows a listener to delete the very object
that is firing the notifications. Do not attempt to further process a11y
notifications for objects that are detached.

Bug:  843960 
Change-Id: I1e10ee014855c1d8f6fbf06c29c5a51c19fe1330
Reviewed-on: https://chromium-review.googlesource.com/1122714
Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org>
Commit-Queue: Aaron Leventhal <aleventhal@chromium.org>
Cr-Commit-Position: refs/heads/master@{#572097}
[modify] https://crrev.com/e0b51b89bac38a15c9e48eba313673b0b32f471f/content/shell/test_runner/web_frame_test_proxy.h

ClusterFuzz has detected this issue as fixed in range 572096:572097.

Detailed report: https://clusterfuzz.com/testcase?key=6374202576470016

Fuzzer: inferno_layout_test_unmodified
Job Type: linux_asan_content_shell_drt
Platform Id: linux

Crash Type: Heap-use-after-free READ 8
Crash Address: 0x61d000025248
Crash State:
  content::RenderFrameImpl::PostAccessibilityEvent
  blink::AXObjectCacheImpl::PostPlatformNotification
  blink::AXObjectCacheImpl::NotificationPostTimerFired
  
Sanitizer: address (ASAN)

Recommended Security Severity: High

Fixed: https://clusterfuzz.com/revisions?job=linux_asan_content_shell_drt&range=572096:572097

Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6374202576470016

See https://github.com/google/clusterfuzz-tools for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.

ClusterFuzz testcase 6374202576470016 is verified as fixed, so closing issue as verified.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.

This does not need any additional merges, as it affects tests only. The bug was in the test runner.

This bug requires manual review: M69 has already been promoted to the beta branch, so this requires manual review
Please contact the milestone owner if you have questions.
Owners: amineer@(Android), kariahda@(iOS), cindyb@(ChromeOS), govind@(Desktop)

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

+awhalley@ (Security TPM) for merge review.

No merge needed.

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