Findit results
---------------
Suspected CLs	The result is a list of CLs that change the crashed files.

Author: yoichio@chromium.org
Project: chromium-blink
Changelist: https://chromium.googlesource.com/chromium/blink.git/+/20224fd8b3427ff492c44ea7ee398c8aef64bd89
Time: Wed Jul 22 08:06:01 2015
Files CompositeEditCommand.cpp, DeleteSelectionCommand.cpp are changed in this cl (and is part of stack frame #5, "blink::CompositeEditCommand::applyCommandToComposite"; frame #6, "blink::CompositeEditCommand::deleteSelection")
Minimum distance from crash line to modified line: 44. (file: CompositeEditCommand.cpp, crashed on: 293, modified: 337).

Suspected Project: chromium-blink
Suspected Component: Blink>Editing

based on Findit results assigning to yoichio@, could you please check and help.

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

ClusterFuzz has detected this issue as fixed in range 434830:434865.

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

Fuzzer: inferno_layout_test_unmodified
Job Type: linux_lsan_chrome_mp
Platform Id: linux

Crash Type: UNKNOWN READ
Crash Address: 0x000000000010
Crash State:
  getFlag
  isConnected
  blink::Node::isDescendantOf
  
Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_lsan_chrome_mp&range=339843:339861
Fixed: https://cluster-fuzz.appspot.com/revisions?job=linux_lsan_chrome_mp&range=434830:434865

Minimized Testcase (1.08 Kb): https://cluster-fuzz.appspot.com/download/AMIfv95ZEFWp-HzCnSVgI9YSRMtXBVBDwKZClxd37IyTPh572GKszVt4LmnvnHzWaQI97dKzI9B8lT7i2I-1uGOM7PlPC6YF8E8mdde345EDPJyu5I-vj2q93aOf4bIHqT94RURx7WOjIce2dqOjd6-8GOlsrpFSeg?testcase_id=5518895232581632

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.