New issue
Advanced search Search tips

Issue 784710 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: Nov 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

CHECK failure: start >= 0 in HTMLToken.h

Project Member Reported by ClusterFuzz, Nov 14 2017

Issue description

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

Fuzzer: libFuzzer_blink_html_tokenizer_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  start >= 0 in HTMLToken.h
  blink::HTMLToken::Attribute::Range::CheckValidStart
  blink::HTMLToken::BeginAttributeName
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=515970:515991

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

Issue filed automatically.

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
 
Project Member

Comment 1 by ClusterFuzz, Nov 14 2017

Components: Blink>HTML>Parser
Labels: Test-Predator-Auto-Components
Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.
Cc: kkaluri@chromium.org
Labels: M-64 Test-Predator-Wrong CF-NeedsTriage
Unable to provide possible suspect using Predator, CL and Code Search.
Could someone please look into the issue.

Thank You...

Comment 3 by kouhei@chromium.org, Nov 15 2017

Cc: kouhei@chromium.org
Owner: lfg@chromium.org
lfg: Would you take a look?
https://chromium-review.googlesource.com/c/chromium/src/+/762016

Comment 4 by lfg@chromium.org, Nov 15 2017

Status: Started (was: Untriaged)
Project Member

Comment 5 by bugdroid1@chromium.org, Nov 16 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/1cb607200f1fd926bfd70326a43406f92f39976a

commit 1cb607200f1fd926bfd70326a43406f92f39976a
Author: Lucas Furukawa Gadani <lfg@chromium.org>
Date: Thu Nov 16 20:32:12 2017

Consume last character when advancing substring in SegmentedString.

Bug:  784710 
Change-Id: I74c7ae6edc0394224b997acd8d7e9fb34105aeba
Reviewed-on: https://chromium-review.googlesource.com/773202
Reviewed-by: Jeremy Roman <jbroman@chromium.org>
Reviewed-by: Kouhei Ueno <kouhei@chromium.org>
Commit-Queue: Lucas Gadani <lfg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#517171}
[modify] https://crrev.com/1cb607200f1fd926bfd70326a43406f92f39976a/third_party/WebKit/Source/platform/text/SegmentedString.cpp
[modify] https://crrev.com/1cb607200f1fd926bfd70326a43406f92f39976a/third_party/WebKit/Source/platform/text/SegmentedStringTest.cpp

Comment 6 by lfg@chromium.org, Nov 16 2017

Status: Fixed (was: Started)
Project Member

Comment 7 by ClusterFuzz, Nov 17 2017

ClusterFuzz has detected this issue as fixed in range 517164:517200.

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

Fuzzer: libFuzzer_blink_html_tokenizer_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  start >= 0 in HTMLToken.h
  blink::HTMLToken::Attribute::Range::CheckValidStart
  blink::HTMLToken::BeginAttributeName
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=515970:515991
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=517164:517200

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

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md 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 8 by ClusterFuzz, Nov 17 2017

Labels: ClusterFuzz-Verified
Status: Verified (was: Fixed)
ClusterFuzz testcase 6169528471126016 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