New issue
Advanced search Search tips

Issue 853555 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

Indirect-leak in es2::Uniform::Uniform

Project Member Reported by ClusterFuzz, Jun 17 2018

Issue description

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

Fuzzer: inferno_twister
Job Type: linux_lsan_chrome_mp
Platform Id: linux

Crash Type: Indirect-leak
Crash Address: 
Crash State:
  es2::Uniform::Uniform
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_lsan_chrome_mp&range=507129:507186

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

Additional requirements: Requires HTTP

Issue filed automatically.

See https://github.com/google/clusterfuzz-tools for more information.
 
Project Member

Comment 1 by ClusterFuzz, Jun 17 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, Jun 17 2018

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

Do not assign a location to uniform block members by sugoi@google.com - https://swiftshader.googlesource.com/SwiftShader/+/ec5da193b1c29dc8bee19dcc8fe297901ff74911

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label.
Cc: kkaluri@chromium.org
sugoi@ Could you please look into this issue...
Cc: -sugoi@google.com capn@chromium.org
It looks like a leak is detected constructing an std::string from another std::string. Weird.
Owner: sugoi@chromium.org
Status: Assigned (was: Untriaged)
Project Member

Comment 6 by ClusterFuzz, Jul 13

Labels: -Reproducible Unreproducible
ClusterFuzz testcase 6113858805301248 appears to be flaky, updating reproducibility label.
Project Member

Comment 7 by ClusterFuzz, Jul 16

Status: WontFix (was: Assigned)
ClusterFuzz testcase 6113858805301248 is flaky and no longer crashes, so closing issue.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
Appears to be a valid indirect result of  Issue 863682 .

Sign in to add a comment