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

Issue 688399 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

Crash in sh::TIntermTraverser::traverseAggregate

Project Member Reported by ClusterFuzz, Feb 3 2017

Issue description

Components: Internals>GPU>ANGLE
Labels: Test-Predator-Wrong M-57
Owner: oetu...@nvidia.com
Status: Assigned (was: Untriaged)
Through code search on file IntermTraverse.cpp, suspected CL is 
https://chromium.googlesource.com/angle/angle.git/+/16c745a3db7875191be2999de4535521b15ba92a
oetuaho@, could you please take a look?
Cc: cwallez@chromium.org jmad...@chromium.org
It's more likely this is just another new fuzzer test case. CC'ing the usual suspects.

Comment 3 by oetu...@nvidia.com, Feb 6 2017

I can't access the test case file for this one for some reason, though I'm marked as the bug owner.
Here you go
clusterfuzz-testcase-5648970404855808
464 bytes View Download

Comment 5 by oetu...@nvidia.com, Feb 6 2017

Owner: ----
Status: Available (was: Assigned)
No repro on latest Chromium. This ANGLE change fixes the issue: https://chromium-review.googlesource.com/c/431001/

If this bug is against an older branch, the fix should be cherry-picked there.
This should be fixed in 447411, with the ANGLE roll. The fuzzer last tested with 447007, so next time it hopefully will pick up the fix.
Cc: -jmad...@chromium.org msrchandra@chromium.org
Owner: jmad...@chromium.org
Status: Assigned (was: Available)
@jmadill -- Could you please update the issue according to the comment# 6.
Thank You.
Status: Fixed (was: Assigned)
Thanks for the heads up. Clusterfuzz detects this as fixed but didn't update the bug. Marking as fixed.
Project Member

Comment 9 by ClusterFuzz, Nov 27 2017

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