kojii@, I've seen that you fixed something pretty similar in  bug 588552 . Could you please take a look?

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

ClusterFuzz has detected this issue as fixed in range 412724:412741.

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

Fuzzer: inferno_twister
Job Type: linux_asan_content_shell_drt
Platform Id: linux

Crash Type: Heap-use-after-free READ 8
Crash Address: 0x611000284f28
Crash State:
  blink::DepthOrderedLayoutObjectList::ordered
  blink::FrameView::layoutOrthogonalWritingModeRoots
  blink::FrameView::performLayout
  
Recommended Security Severity: High

Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_asan_content_shell_drt&range=407480:407721
Fixed: https://cluster-fuzz.appspot.com/revisions?job=linux_asan_content_shell_drt&range=412724:412741

Minimized Testcase (0.81 Kb): https://cluster-fuzz.appspot.com/download/AMIfv95vli4dZn3Z2mB4s3YZh6PgDyGt7ef9LK8eP04Xs_TvvlupSS-EfW1Gau64QIXzhZygoGrVSj3nB62Xfj3j5xqr46D6p9c1aI83lhbJ8mFe-gV5eLsg4uDtZAuocfKBAYVAI5C_L_oLLvbEAKfPvAgm290-ag?testcase_id=5041010575147008

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.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/119d9ebab5f2682ec5b3afe35ed078a80ae08635

commit 119d9ebab5f2682ec5b3afe35ed078a80ae08635
Author: kojii <kojii@chromium.org>
Date: Fri Aug 19 08:55:07 2016

Avoid LayoutFullScreen to be orthogonal writing-mode roots when reattached

The previous CL to avoid LayoutFullScreen to be orthogonal writing-mode
roots[1] copied the writing-mode when adding it to the parent. However,
when reattach occurs, LayoutTreeBuilder creates LayoutFullScreen
before the target is added to the parent, and thus LayoutFullScreen
fails to copy from the parent.

This patch copies the writing-mode when creating LayoutFullScreen.

[1] http://crrev.com/1721653002

BUG= 638571 

Review-Url: https://codereview.chromium.org/2258973002
Cr-Commit-Position: refs/heads/master@{#413089}

[add] https://crrev.com/119d9ebab5f2682ec5b3afe35ed078a80ae08635/third_party/WebKit/LayoutTests/fullscreen/orthogonal-writing-mode-full-screen-reattach-crash-expected.txt
[add] https://crrev.com/119d9ebab5f2682ec5b3afe35ed078a80ae08635/third_party/WebKit/LayoutTests/fullscreen/orthogonal-writing-mode-full-screen-reattach-crash.html
[modify] https://crrev.com/119d9ebab5f2682ec5b3afe35ed078a80ae08635/third_party/WebKit/Source/core/layout/LayoutFullScreen.cpp
[modify] https://crrev.com/119d9ebab5f2682ec5b3afe35ed078a80ae08635/third_party/WebKit/Source/core/layout/LayoutFullScreen.h
[modify] https://crrev.com/119d9ebab5f2682ec5b3afe35ed078a80ae08635/third_party/WebKit/Source/core/layout/LayoutObject.cpp
[modify] https://crrev.com/119d9ebab5f2682ec5b3afe35ed078a80ae08635/third_party/WebKit/Source/core/layout/LayoutObject.h

ClusterFuzz testcase is verified as fixed, closing issue.

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