Automatically adding ccs based on OWNERS file / target commit history.

If this is incorrect, please add ClusterFuzz-Wrong label.

This issue looks similar to  bug 834570 , hence assigning to the same owner for more updates. 

piman@ Could you please take a look in to this issue?

Thanks!

https://chromium-review.googlesource.com/c/chromium/src/+/1096296 fixes this locally.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/30a1acd5c3e233f4105d04289a5d4907fc09e589

commit 30a1acd5c3e233f4105d04289a5d4907fc09e589
Author: Antoine Labour <piman@chromium.org>
Date: Wed Jun 13 21:04:44 2018

Use a fixed sized buffer for simulated attrib 0 uploads

This avoids allocating arbitrary large buffers, which could fail or cause
unnecessary fragmentation.

Bug:  844854 
Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel
Change-Id: Ib7f0f14628fdb26c7efad08c26aba77d4b20095c
Reviewed-on: https://chromium-review.googlesource.com/1096296
Reviewed-by: Zhenyao Mo <zmo@chromium.org>
Commit-Queue: Antoine Labour <piman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#566981}
[modify] https://crrev.com/30a1acd5c3e233f4105d04289a5d4907fc09e589/gpu/command_buffer/service/gles2_cmd_decoder.cc

ClusterFuzz has detected this issue as fixed in range 566973:566988.

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

Fuzzer: libFuzzer_gpu_fuzzer
Job Type: libfuzzer_chrome_msan
Platform Id: linux

Crash Type: Out-of-memory (exceeds 2048 MB)
Crash Address: 
Crash State:
  gpu_fuzzer
  
Sanitizer: memory (MSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=512673:512693
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=566973:566988

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

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md 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 6575132139847680 is verified as fixed, so closing issue as verified.

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