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

Issue 870738 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Last visit 18 days ago
Closed: Aug 16
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

ASSERT: 0 && "Unhandled SPIR-V target environment"

Project Member Reported by ClusterFuzz, Aug 3

Issue description

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

Fuzzer: libFuzzer_spvtools_val_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: ASSERT
Crash Address: 
Crash State:
  0 && "Unhandled SPIR-V target environment"
  spvTargetEnvDescription
  spvtools::val::VersionCheck
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=579911:580305

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

Issue filed automatically.

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

Comment 1 by ClusterFuzz, Aug 3

Components: Internals>GPU>Internals
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: alanbaker@google.com
Owner: dsinclair@chromium.org
Status: Assigned (was: Untriaged)
Cc: -alanbaker@google.com dsinclair@chromium.org
Owner: alanbaker@google.com
Status: WontFix (was: Assigned)
This function returns a reasonable empty string that is only used for messaging in release mode. The assert is useful for internal development.
Project Member

Comment 5 by ClusterFuzz, Aug 23

Labels: Needs-Feedback
ClusterFuzz testcase 5689560001150976 is still reproducing on tip-of-tree build (trunk).

If this testcase was not reproducible locally or unworkable, ignore this notification and we will file another bug soon with hopefully a better and workable testcase.

Otherwise, if this is not intended to be fixed (e.g. this is an intentional crash), please add ClusterFuzz-Ignore label to prevent future bug filing with similar crash stacktrace.
This is something we don't plan on fixing as it's only triggered in debug mode.
Cc: pnangunoori@chromium.org
 Issue 879369  has been merged into this issue.
Cc: kkaluri@chromium.org
 Issue 879918  has been merged into this issue.

Sign in to add a comment