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

Issue 844533 link

Starred by 3 users
Status: Fixed
Owner: ----
Closed: Nov 20
Cc:
█ brajkumar@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug



Sign in to add a comment

Null-dereference READ in C:\Windows\SYSTEM32\d3d10warp.dll

Project Member Reported by ClusterFuzz, May 18 2018 
Detailed report: https://clusterfuzz.com/testcase?key=6495427491528704

Fuzzer: inferno_twister
Job Type: windows_asan_chrome_no_sandbox
Platform Id: windows

Crash Type: Null-dereference READ
Crash Address: 0x000000000008
Crash State:
  C:\Windows\SYSTEM32\d3d10warp.dll
  C:\Windows\SYSTEM32\d3d10warp.dll
  C:\Windows\SYSTEM32\d3d10warp.dll
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=windows_asan_chrome_no_sandbox&range=541484:541517

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

Issue filed automatically.

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

Comment 1 by brajkumar@chromium.org, May 22 2018

Cc: brajkumar@chromium.org
Components: Internals
Labels: M-67 Test-Predator-Wrong CF-NeedsTriage
Unable to find actual suspect through code search and also observing no related CL's under regression range, hence adding appropriate label and requesting someone from internals team to look in to this issue.

Thanks!

Comment 2 by brajkumar@chromium.org, May 28 2018 

 Issue 847066  has been merged into this issue.

Comment 3 by manoranjanr@google.com, Nov 20

Labels: -CF-NeedsTriage
Status: Fixed (was: Untriaged)
The CF report (https://clusterfuzz.com/testcase-detail/6495427491528704) says, it has been 'Fixed'.
Project Member

Comment 4 by ClusterFuzz, Nov 27

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

Please re-test your fix against this testcase and if the fix was incorrect or incomplete, please re-open the bug. Otherwise, ignore this notification and add ClusterFuzz-Wrong label.
►

Sign in to add a comment