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

(Security Sheriff Triage)
Seems to be related to https://codereview.chromium.org/2981083002

Yes. Reverted cl and will reland with fix.

Revert: https://codereview.chromium.org/2988753002/

Issue 748571 has been merged into this issue.

ClusterFuzz has detected this issue as fixed in range 489286:489347.

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

Fuzzer: meacer_extension_apis
Job Type: windows_syzyasan_chrome
Platform Id: windows

Crash Type: Heap-use-after-free READ 1
Crash Address: 0x2d4c6a80
Crash State:
  ui::AXPlatformNodeWin::Destroy
  content::LegacyRenderWidgetHostHWND::~LegacyRenderWidgetHostHWND
  content::LegacyRenderWidgetHostHWND::OnFinalMessage
  
Memory Tool: SYZYASAN

Recommended Security Severity: High

Regressed: https://clusterfuzz.com/revisions?job=windows_syzyasan_chrome&range=489104:489186
Fixed: https://clusterfuzz.com/revisions?job=windows_syzyasan_chrome&range=489286:489347

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


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 4532749481541632 is verified as fixed, so closing issue as verified.

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