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

This looks the same as  crbug.com/668553  - can you confirm and merge it if so? Thanks!

>#c4 
It seems the root cause is as same as  crbug.com/668533 .
The bug is triggered by execCommand but editing isn't the root cause.

I guess we're talking about  issue 668553 .

Confirmed that fixing  issue 668553  also makes this go away.

ClusterFuzz has detected this issue as fixed in range 434769:434840.

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

Fuzzer: bj_broddelwerk
Job Type: linux_msan_chrome
Platform Id: linux

Crash Type: Use-of-uninitialized-value
Crash Address: 
Crash State:
  blink::PaintLayer::setNeedsCompositingInputsUpdate
  blink::RootScrollerController::recomputeEffectiveRootScroller
  blink::FrameView::layout
  
Recommended Security Severity: Medium

Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_msan_chrome&range=434315:434385
Fixed: https://cluster-fuzz.appspot.com/revisions?job=linux_msan_chrome&range=434769:434840

Minimized Testcase (4.13 Kb): https://cluster-fuzz.appspot.com/download/AMIfv94ObGbr5NE--CT4Ja1lm5TbIq2ZT3Ws4VtsEMaEVYl80Icb1YYcEbdb-UFJPu1R1sTrIhoFrLRRv90dV6EHHuvVM4TUyZt_LKf0udGPKpDFOCXzq6PTIkubjJyRCA-cEMQDGAXFqTC6lK4p-yMpn2gFZjRGWw?testcase_id=5740009186656256

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