Regression information is not available. The result is the blame information.

Author: dsinclair@chromium.org
Project: chromium
Changelist: https://chromium.googlesource.com/chromium/src//+/735bbbde69644fc8a35d022b715c9db905b52846
Time: Thu Feb 26 16:03:40 2015
The CL last changed line 216 of file LayoutBlockFlow.cpp, which is stack frame 5.

Suspected Project: chromium
Suspected Component: Blink>Layout
=====================================
Above mentioned is the CL's list from findit, Suspecting the file of "LayoutBlockFlow.cpp" from the frame #5 .

dsinclair@: Could you please look into this issue if it is related to your change, else please help us in assigning it to the right owner.

Thanks!

eae@ for layout-dev triage.

ClusterFuzz has detected this issue as fixed in range 420372:420465.

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

Fuzzer: mbarbella_js_mutation_layout
Job Type: linux_debug_content_shell_drt
Platform Id: linux

Crash Type: ASSERT
Crash Address: 
Crash State:
  containingBlock->isLayoutInline() && containingBlock->isInFlowPositioned()
  blink::LayoutBox::containingBlockLogicalWidthForPositioned
  blink::LayoutBox::computePositionedLogicalWidth
  
Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_debug_content_shell_drt&range=358612:358651
Fixed: https://cluster-fuzz.appspot.com/revisions?job=linux_debug_content_shell_drt&range=420372:420465

Minimized Testcase (0.30 Kb):
Download: https://cluster-fuzz.appspot.com/download/AMIfv94O0ybkNlzzEU4k1pGxWJQ7CJrrbhlholix2GTMwmEqEK0-TGQ8vB_cJjRvLMcWrwk3GXhgw00p7gXXyL6wNFy_FJpKmdYuIIKDboiIoUDntGqdDAURlpvDAHtmOzFrCBXit2dm5TVKkK1aygoO9_LLtgr2iQ?testcase_id=5298563369664512
<style>
   .class1 { position: relative; }
.class2 { position: absolute;</style>
  <script>
window.onload = function() {
    document.designMode="on";
    document.execCommand("SelectAll");
    document.execCommand("Strikethrough");
}
</script>
  <i class="class1">
   <div>
    <xmp class="class2">
     A


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.

ClusterFuzz testcase is verified as fixed, closing issue.

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

Removing EditIssue view restrictions from ClusterFuzz filed bugs. If you believe that this issue should still be restricted, please reapply the label.

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