New issue
Advanced search Search tips

Issue 712476 link

Starred by 1 user

Issue metadata

Status: Verified
Owner: ----
Closed: Jun 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows , All
Pri: 3
Type: Bug



Sign in to add a comment

Crash in blink::CreateMarkupAlgorithm<class blink::EditingAlgorithm<class blink::NodeTrav

Project Member Reported by ClusterFuzz, Apr 18 2017

Issue description

Components: Blink>Editing>Command
Labels: M-60 Test-Predator-Wrong
Owner: yoichio@chromium.org
Status: Assigned (was: Untriaged)
Through code search on file CompositeEditCommand.cpp, suspected CL is 
https://chromium.googlesource.com/chromium/src/+/8e45386fb683e55cd2354e5537c352b3cf8303c6%5E%21/#F2
yoichio@, could you please take a look?
Thank you.
Labels: -OS-Windows -Pri-1 -Stability-Memory-AddressSanitizer -M-60 OS-All Pri-2
Owner: ----
It is just refactoring.
Project Member

Comment 3 by ClusterFuzz, Apr 18 2017

Labels: OS-Windows

Comment 4 by yosin@chromium.org, May 22 2017

Labels: Pri-3
Bulk set to Pri-3 for cluster fuzz bugs.
Since these issues are happens with unusual HTML.
Project Member

Comment 5 by ClusterFuzz, Jun 14 2017

ClusterFuzz has detected this issue as fixed in range 479249:479283.

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

Fuzzer: bj_broddelwerk
Job Type: windows_asan_chrome_no_sandbox
Platform Id: windows

Crash Type: Null-dereference READ
Crash Address: 0x00000000
Crash State:
  blink::CreateMarkupAlgorithm<class blink::EditingAlgorithm<class blink::NodeTrav
  blink::CreateMarkup
  blink::CompositeEditCommand::MoveParagraphs
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=windows_asan_chrome_no_sandbox&range=456190:456233
Fixed: https://clusterfuzz.com/revisions?job=windows_asan_chrome_no_sandbox&range=479249:479283

Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6063175683538944


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.
Project Member

Comment 6 by ClusterFuzz, Jun 14 2017

Labels: ClusterFuzz-Verified
Status: Verified (was: Assigned)
ClusterFuzz testcase 6063175683538944 is verified as fixed, so closing issue.

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

Sign in to add a comment