New issue
Advanced search Search tips

Issue 814358 link

Starred by 1 user
Status: WontFix
Owner:
capn@chromium.org
Closed: Apr 2018
Cc:
sugoi@google.com
sugoi@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Integer-overflow in TType::elementRegisterCount

Project Member Reported by ClusterFuzz, Feb 21 2018 
Detailed report: https://clusterfuzz.com/testcase?key=6315154707578880

Fuzzer: libFuzzer_swiftshader_vertex_routine_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

Crash Type: Integer-overflow
Crash Address: 
Crash State:
  TType::elementRegisterCount
  TType::totalRegisterCount
  TType::elementRegisterCount
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=529109:529114

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

Issue filed automatically.

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

Comment 1 by ClusterFuzz, Feb 21 2018

Components: Internals>GPU>SwiftShader
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.
Project Member

Comment 2 by ClusterFuzz, Feb 21 2018

Cc: sugoi@google.com
Labels: Test-Predator-Auto-CC
Automatically adding ccs based on suspected regression changelists:

Sampler allocation fix by sugoi@google.com - https://swiftshader.googlesource.com/SwiftShader/+/da163edbdc41cbccacfd526f51b2cd2a9b6267bf

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label.

Comment 3 by brajkumar@chromium.org, Feb 22 2018

Owner: capn@chromium.org
Status: Assigned (was: Untriaged)
The above issue is related to swiftshader, hence assigning to @capn for more updates on this issue.

Thanks!
Project Member

Comment 4 by ClusterFuzz, Apr 26 2018

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