dcheng@, you modified some part of the stacktrace recently (https://chromium.googlesource.com/chromium/src/+/84512f5a48edc83ac61bd8fe5dff0f4743a8595e), would you mind taking a look or helping to find an owner?

ClusterFuzz has detected this issue as fixed in range 412469:412479.

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

Fuzzer: lcamtuf_cross_fuzz
Job Type: linux_asan_chrome_chromeos
Platform Id: linux

Crash Type: ASSERT
Crash Address: 
Crash State:
  !m_deletionHasBegun
  blink::StyleResolverState::StyleResolverState
  blink::StyleResolverState::StyleResolverState
  
Fixed: https://cluster-fuzz.appspot.com/revisions?job=linux_asan_chrome_chromeos&range=412469:412479

Unminimized Testcase: https://cluster-fuzz.appspot.com/download/AMIfv97JeGYMrJEDIrIr9eME6NaMe49wCTEv6ZohvIo_ndogL2ah2gszDAdXwkYGXnnSbpRkvvhN4is0PGfT0Zz2WRKq_DFdhKYxDPyJKSpLiz6vDaM03pGq54epYyB8NlobIuP5dCamaVY8PbIPMP--m7_tZ6d-3Ai4r2-5blCbuHU2DriOahY?testcase_id=6141046524477440


See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.

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

Maybe fixed by https://chromium.googlesource.com/chromium/src/+/c739b16ff7c5b84fcd4620df5d46c419563c2ef7? I'm honestly not sure, since I'm not familiar with this part of the system.

ClusterFuzz testcase is verified as fixed, closing issue.

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

Not sure what the cause was, trusting clusterfuzz and marking as fixed

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