Author: mjs@apple.com
Project: chromium
Changelist: https://chromium.googlesource.com/chromium/src/+/554c7634cddfec7925865257d362fa718c34ac3a
Time: Thu May 06 22:41:15 2010
The CL last changed line 711 of file Node.h, which is stack frame 0.

Author: yoichio
Project: chromium
Changelist: https://chromium.googlesource.com/chromium/src/+/52032ceee8e754efb8100f977b92f8dbf1f6e30a
Time: Wed Oct 21 02:03:58 2015
The CL last changed line 619 of file EditingUtilities.cpp, which is stack frame 3.

@yoichio: Assigning to you, Request you to please take a look into it. Please help us to reassign if not with respect to your change.

Reproduced Version 55.0.2881.5 canary (64-bit) on win.

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 455091:455392.

Detailed report: https://clusterfuzz.com/testcase?key=5568131814916096

Fuzzer: attekett_dom_fuzzer
Job Type: linux_asan_chrome_media
Platform Id: linux

Crash Type: UNKNOWN READ
Crash Address: 0x000000000010
Crash State:
  blink::PositionTemplate<blink::EditingAlgorithm<blink::NodeTraversal> >::lastPos
  blink::PositionTemplate<blink::EditingAlgorithm<blink::NodeTraversal> > blink::l
  blink::lastEditablePositionBeforePositionInRoot
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_media&range=371266:371316
Fixed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_media&range=455091:455392

Reproducer Testcase: https://clusterfuzz.com/download/AMIfv95eKHvY1rrr4rZITdP1GrbTWQx7y_ejrMmXTT65BT4FZB8IXgb9ucUS8YWt2jxEf1j0hUDFetA6njebAxBrBCc_qf7HV-JB_TrNYWwedSKZ22rX2akJFvQHHWVaCQKVDYQfz6vgGk57iclOlBuijfa4vQoQ3Q?testcase_id=5568131814916096


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 5568131814916096 is verified as fixed, so closing issue.

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