New issue
Advanced search Search tips

Issue 795605 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

Sanitizer CHECK failure in "(("unable to unmap" && 0)) != (0)" (0x0, 0x0)

Project Member Reported by ClusterFuzz, Dec 17 2017

Issue description

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

Fuzzer: ochang_domfuzzer
Job Type: linux_tsan_chrome_mp
Platform Id: linux

Crash Type: Sanitizer CHECK failure
Crash Address: 
Crash State:
  "(("unable to unmap" && 0)) != (0)" (0x0, 0x0)
  
Sanitizer: thread (TSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_tsan_chrome_mp&range=399407:399414

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

Issue filed automatically.

See https://github.com/google/clusterfuzz-tools for more information.
 
Cc: kkaluri@chromium.org
Components: Internals
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.
Project Member

Comment 2 by ClusterFuzz, Dec 28 2017

ClusterFuzz has detected this issue as fixed in range 526241:526242.

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

Fuzzer: ochang_domfuzzer
Job Type: linux_tsan_chrome_mp
Platform Id: linux

Crash Type: Sanitizer CHECK failure
Crash Address: 
Crash State:
  "(("unable to unmap" && 0)) != (0)" (0x0, 0x0)
  
Sanitizer: thread (TSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_tsan_chrome_mp&range=399407:399414
Fixed: https://clusterfuzz.com/revisions?job=linux_tsan_chrome_mp&range=526241:526242

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

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

Comment 3 by ClusterFuzz, Dec 28 2017

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