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

eae@, could you please help to find an owner for another Layout crash?

No layout changes in regression range, crash in sticky impl; over to flackr.

Friendly reminder to look into this bug as it's a P1 security bug marked as a release blocker.

This is probably the same as  issue 679170  but hopefully I can reproduce this failure.

I was able to reproduce and bisect the problem. This seems to have regressed with 1b236220b372cebf8ca953af180c1824e478de16 though I'm surprised that an experimental feature would affect content_shell, does it content_shell run with experimental features enabled?

Should we revert this until we identify the underlying cause?

Yes content_shell in layout test mode is run with experimental features enabled. We do this to expose problems earlier for experimental features. Will fix this instead of reverting because this doesn't affect users for now.

Merge into  bug 679170  because the proposed CL will also fix this bug.

ClusterFuzz has detected this issue as fixed in range 444813:444844.

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

Fuzzer: inferno_twister
Job Type: mac_asan_content_shell
Platform Id: mac

Crash Type: Heap-use-after-free READ 8
Crash Address: 0x60f000050b98
Crash State:
  blink::LayoutBoxModelObject::invalidateStickyConstraints
  blink::LayoutBlock::updateAfterLayout
  blink::LayoutBlockFlow::layoutBlock
  
Sanitizer: address (ASAN)

Recommended Security Severity: High

Regressed: https://cluster-fuzz.appspot.com/revisions?job=mac_asan_content_shell&range=441240:441358
Fixed: https://cluster-fuzz.appspot.com/revisions?job=mac_asan_content_shell&range=444813:444844

Minimized Testcase (0.32 Kb): https://cluster-fuzz.appspot.com/download/AMIfv97D4KQEauBi977pCHs0J8m8o2vWKOQqJlMtdWC2RbzO27BYEa5tqkF2njenCV13SmZ7NwGebQBZ7opRkvq6yETWcxort_P5TM5ACEDc_RgeTheOBvc4bGndhoADb7n1YRcnD8SRBQu36f9tktGqpArNrrzBjsuzhkx7xR5l7NS7bKKxCFN5E5dOLRbThtqIVTG7a3Kxn8srCCy03fuKNnARJyi9dMb0J0kn1lWg-x9Xc54_HNwaR789svpIS9__rY_Vf6jEZXc1DrwDiMy_6W9_kEgbA_r0w7_zjHxo9Ts_H15JOSrwU372aX7mrmBIdI5PyP41yaVEdXh3EPI9uSeCEb04FqflXJxsoY0FeMgII8E5Y93V-geD6PtgNeNM2Kr0QjSVzKbuEQpYMRj3riJgc9nHKg?testcase_id=6037737645015040

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.

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