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

Issue 764752 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

Sanitizer CHECK failure in ((0)) != (0) (0, 0)

Project Member Reported by ClusterFuzz, Sep 13 2017

Issue description

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

Fuzzer: libFuzzer_pdf_codec_gif_fuzzer
Job Type: libfuzzer_chrome_msan
Platform Id: linux

Crash Type: Sanitizer CHECK failure
Crash Address: 
Crash State:
  ((0)) != (0) (0, 0)
  
Sanitizer: memory (MSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=501422:501484

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

Issue filed automatically.

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md for more information.
 
Components: Blink>MemoryAllocator
Labels: M-63 CF-NeedsTriage Test-Predator-Wrong
Predator, Code Search and CL could not provide any possible suspects.
Adding CF-NeedsTriage for further inputs.
Thank You.
Cc: alekseys@chromium.org
These allocator failures produce very poor report.
Could we add a description of the failure and a stack trace?
Project Member

Comment 3 by ClusterFuzz, Sep 14 2017

Status: WontFix (was: Untriaged)
ClusterFuzz testcase 4515898340933632 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