New issue
Advanced search Search tips

Issue 881349 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

Out-of-memory in spvtools_opt_legalization_fuzzer

Project Member Reported by ClusterFuzz, Sep 6

Issue description

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

Fuzzer: libFuzzer_spvtools_opt_legalization_fuzzer
Job Type: libfuzzer_chrome_msan
Platform Id: linux

Crash Type: Out-of-memory (exceeds 2048 MB)
Crash Address: 
Crash State:
  spvtools_opt_legalization_fuzzer
  
Sanitizer: memory (MSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=581972:581986

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

Issue filed automatically.

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
 
Cc: dsinclair@chromium.org
Components: Internals>GPU>Internals
Owner: stevenperron@google.com
Status: Assigned (was: Untriaged)
Looks like the validator is using 4933 MB of memory.  It uses just as much if compact the ids.  I opened issue https://github.com/KhronosGroup/SPIRV-Tools/issues/1882 to track it.
Project Member

Comment 3 by ClusterFuzz, Sep 19

ClusterFuzz has detected this issue as fixed in range 591971:592067.

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

Fuzzer: libFuzzer_spvtools_opt_legalization_fuzzer
Job Type: libfuzzer_chrome_msan
Platform Id: linux

Crash Type: Out-of-memory (exceeds 2048 MB)
Crash Address: 
Crash State:
  spvtools_opt_legalization_fuzzer
  
Sanitizer: memory (MSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=581972:581986
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=591971:592067

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

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 4 by ClusterFuzz, Sep 19

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