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

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

ClusterFuzz has detected this issue as fixed in range 421612:421673.

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=6546863803334656

Fuzzer: libfuzzer_ax_tree_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: Heap-use-after-free READ 4
Crash Address: 0x6130000007b8
Crash State:
  ui::AXNode::id
  ui::AXTreeUpdateState::HasChangedNode
  ui::AXTree::DestroySubtree
  
Recommended Security Severity: High

Regressed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_asan_debug&range=418280:418374
Fixed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_asan_debug&range=421612:421673

Minimized Testcase (0.02 Kb): https://cluster-fuzz.appspot.com/download/AMIfv95mviz-AZEUYEWQM3qRDnZ6wu8AWpe_6f9CQp1Z3BRM30L1HbNz5Zxsn97L768Wn4BT0JjvlTLlrEHc4_QMGKFrXehZAtu1NqYcXFwGFXYo09Y_4DcwGlZpSoyT2uSZ8kcu1-IQLgmnyNq5payy3Mh6hcvknA?testcase_id=6546863803334656

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md 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 is verified as fixed, closing issue.

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

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