Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.

Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/6761ee0e50cc34c67d37bd5fa2d39c231dd7df17 (Implement TextEncoderStream and TextDecoderStream).

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.

The crash appears to be an intentional one based on the stack, but how it is being triggered by the repro is a total mystery to me.

Neither the stack nor the code in the repro have anything to do with my change.

Predator and CL did not provide any possible suspects.

Using Code Search for the file, "gl_utils.cc" assigning to the concern owner.

Suspecting Commit : https://chromium.googlesource.com/chromium/src/+/3689f3e57b85ca683cc6b61841715fbd0c6af559

kbr@ -- Could you please look into the issue, kindly re-assign if this is not related to your changes.


Thank You.

This has come up before in for example Issue 871749. Clusterfuzz needs to stop fuzzing this entry point if it's passing the --enable-gpu-benchmarking command line flag. Abhishek, could you please change the fuzzer to stop calling this?

ClusterFuzz has detected this issue as fixed in range 589711:589712.

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

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=588442:588443
Fixed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_content_shell_drt&range=589711:589712

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

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

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.

ClusterFuzz testcase 5548305153785856 is verified as fixed, so closing issue as verified.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.

Added a stack blacklist using "in\sgl::Crash\(", gl::Crash can never be from real code, excluding.