New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 843259 link

Starred by 2 users
Status: WontFix
Owner:
█ jcivelli@chromium.org
Last visit > 30 days ago
Closed: Aug 10
Cc:
pnangunoori@chromium.org
█ jcivelli@google.com
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

Timeout in xml_parser_fuzzer

Project Member Reported by ClusterFuzz, May 15 2018 
Detailed report: https://clusterfuzz.com/testcase?key=4789283408576512

Fuzzer: libFuzzer_xml_parser_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

Crash Type: Timeout (exceeds 25 secs)
Crash Address: 
Crash State:
  xml_parser_fuzzer
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=558655:558657

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

Issue filed automatically.

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

Comment 1 by ClusterFuzz, May 15 2018

Cc: jcivelli@google.com
Labels: ClusterFuzz-Auto-CC
Automatically adding ccs based on OWNERS file / target commit history.

If this is incorrect, please add ClusterFuzz-Wrong label.
Project Member

Comment 2 by ClusterFuzz, May 16 2018

Labels: -Reproducible Unreproducible
ClusterFuzz testcase 4789283408576512 appears to be flaky, updating reproducibility label.

Comment 3 by pnangunoori@chromium.org, May 16 2018

Cc: pnangunoori@chromium.org
Labels: Test-Predator-Wrong
Owner: schenney@chromium.org
Status: Assigned (was: Untriaged)
As per the  Issue 808446  owner, assigning this issue to @schenney.
@schenney -- Could you please look into this issue, kindly reassign if it has nothing to do with your changes.
Thanks.

Comment 4 by schenney@chromium.org, May 16 2018

Components: Blink>XML Tools>Stability>ClusterFuzz
Owner: jcivelli@chromium.org
Over to someone who has changed the fuzzer.

Comment 5 by infe...@chromium.org, May 21 2018

Components: -Tools>Stability>ClusterFuzz
Project Member

Comment 6 by ClusterFuzz, Aug 10

Status: WontFix (was: Assigned)
ClusterFuzz testcase 4789283408576512 is flaky and no longer crashes, so closing issue.

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

Sign in to add a comment