CompositeEditCommand::MoveParagraphs crashes due to moving destination out of document during InsertOrderedList command |
||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=4650671835185152 Fuzzer: bj_broddelwerk Job Type: windows_asan_chrome_no_sandbox Platform Id: windows Crash Type: Null-dereference READ Crash Address: 0x00000000 Crash State: blink::TextIteratorAlgorithm<class blink::EditingAlgorithm<class blink::NodeTrav blink::TextIteratorAlgorithm<class blink::EditingAlgorithm<class blink::NodeTrav blink::CompositeEditCommand::MoveParagraphs Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=windows_asan_chrome_no_sandbox&range=443500:443512 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4650671835185152 Issue filed automatically. See https://github.com/google/clusterfuzz-tools for more information.
,
Jul 29 2017
CompositeEditCommand::MoveParagraphs (once again) moves |destination| out of document. Lower to P3 due to low usage of InsertOrderedList command and uncommon HTML.
,
Jul 29 2017
,
Jul 30 2017
Issue 723283 has been merged into this issue.
,
Aug 19 2017
ClusterFuzz has detected this issue as fixed in range 495542:495750. Detailed report: https://clusterfuzz.com/testcase?key=4650671835185152 Fuzzer: bj_broddelwerk Job Type: windows_asan_chrome_no_sandbox Platform Id: windows Crash Type: Null-dereference READ Crash Address: 0x00000000 Crash State: blink::TextIteratorAlgorithm<class blink::EditingAlgorithm<class blink::NodeTrav blink::TextIteratorAlgorithm<class blink::EditingAlgorithm<class blink::NodeTrav blink::CompositeEditCommand::MoveParagraphs Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=windows_asan_chrome_no_sandbox&range=443500:443512 Fixed: https://clusterfuzz.com/revisions?job=windows_asan_chrome_no_sandbox&range=495542:495750 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4650671835185152 See https://github.com/google/clusterfuzz-tools for more information. If you suspect that the result above is incorrect, try re-doing that job on the test case report page.
,
Aug 19 2017
ClusterFuzz testcase 4650671835185152 is verified as fixed, so closing issue as verified. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue. |
||||
►
Sign in to add a comment |
||||
Comment 1 by msrchandra@chromium.org
, Jul 27 2017Labels: M-62 Test-Predator-Wrong
Owner: xiaoche...@chromium.org
Status: Assigned (was: Untriaged)