Crash in blink::CompositeEditCommand::insertNodeBefore |
|||||||
Issue descriptionDetailed report: https://cluster-fuzz.appspot.com/testcase?key=4969403016019968 Fuzzer: bj_broddelwerk Job Type: windows_syzyasan_chrome Platform Id: windows Crash Type: UNKNOWN Crash Address: 0x0000000b Crash State: blink::CompositeEditCommand::insertNodeBefore blink::ReplaceSelectionCommand::mergeEndIfNeeded blink::ReplaceSelectionCommand::doApply Regressed: https://cluster-fuzz.appspot.com/revisions?job=windows_syzyasan_chrome&range=400073:400083 Minimized Testcase (4.14 Kb): https://cluster-fuzz.appspot.com/download/AMIfv97u7GggCWx12f7p3eImNJosY87oO6fHplXR5sdhQ19CrS_tX5yvCSyMIcoh_y01vHn0WjgZqOREVe5E-sB_KA1bpihxhw-KKwM95D4khtbrUzF3ZVzjsdFoLgqdMMJGb73WT0bnnW9L7TiIc7JKxhL46y9WzA Filer: durga.behera See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.
,
Jun 17 2016
,
Jun 17 2016
Moving this nonessential bug to the next milestone. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 4 2016
This issue is Pri-1 but has already been moved once. Lowering the priority and moving to the next milestone. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 7 2016
ClusterFuzz has detected this testcase as flaky and is unable to reproduce it in the original crash revision. Skipping fixed testing check and marking it as potentially fixed. Detailed report: https://cluster-fuzz.appspot.com/testcase?key=4969403016019968 Fuzzer: bj_broddelwerk Job Type: windows_syzyasan_chrome Platform Id: windows Crash Type: UNKNOWN Crash Address: 0x0000000b Crash State: blink::CompositeEditCommand::insertNodeBefore blink::ReplaceSelectionCommand::mergeEndIfNeeded blink::ReplaceSelectionCommand::doApply Regressed: https://cluster-fuzz.appspot.com/revisions?job=windows_syzyasan_chrome&range=400073:400083 Minimized Testcase (4.14 Kb): https://cluster-fuzz.appspot.com/download/AMIfv97u7GggCWx12f7p3eImNJosY87oO6fHplXR5sdhQ19CrS_tX5yvCSyMIcoh_y01vHn0WjgZqOREVe5E-sB_KA1bpihxhw-KKwM95D4khtbrUzF3ZVzjsdFoLgqdMMJGb73WT0bnnW9L7TiIc7JKxhL46y9WzA?testcase_id=4969403016019968 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.
,
Jul 8 2016
Mark WontFix according to #c5 and I could not reproduce on ToT and M53 cannary
,
Oct 18 2016
,
Nov 22 2016
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 |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by durga.behera@chromium.org
, Jun 17 2016Owner: yosin@chromium.org
Status: Assigned (was: Available)