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

Issue 871661 link

Starred by 1 user
Status: Duplicate
Owner:
█ kbr@chromium.org
OOO until 2019-01-24
Closed: Aug 8
Cc:
kkaluri@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

Null-dereference WRITE in gl::Crash

Project Member Reported by ClusterFuzz, Aug 7 
Detailed report: https://clusterfuzz.com/testcase?key=5070686754963456

Fuzzer: inferno_twister
Job Type: linux_ubsan_vptr_content_shell_drt
Platform Id: linux

Crash Type: Null-dereference WRITE
Crash Address: 0x000000000000
Crash State:
  gl::Crash
  bool IPC::MessageT<GpuChannelMsg_CrashForTesting_Meta, std::__1::tuple<>, void>:
  gpu::GpuChannel::OnControlMessageReceived
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_content_shell_drt&range=581064:581078

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

Issue filed automatically.

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

Comment 1 by kkaluri@chromium.org, Aug 8

Cc: kkaluri@chromium.org
Labels: M-70
Owner: kbr@chromium.org
Status: Assigned (was: Untriaged)
Predator has provided with one possible suspect, hence assigning to concern owner for further triage

Suspect CL: https://chromium.googlesource.com/chromium/src/+/3689f3e57b85ca683cc6b61841715fbd0c6af559

kbr@ Could you please look into this issue.

Comment 2 by kbr@chromium.org, Aug 8

Mergedinto: 871749
Status: Duplicate (was: Assigned)
I don't know where the command line flags are being set in the fuzzing harness, but this definitely isn't accessible from the renderer process unless --enable-gpu-benchmarking is being passed on the command line.
►

Sign in to add a comment