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

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

Predator has provided 8 possible suspects

1. fix broken flatten example and update usingBookmaker by caryclark@skia.org
2. oop: Fix nullptr dereference in a fuzz test case. by vmpstr@chromium.org
3. Get rid of GpuDataManagerImpl::UpdateRendererPrefs(). by zmo@chromium.org
4. Remove SkColorSpace_Base::MakeNamed, along with most uses of Adobe RGB by brianosman@google.com
5. pre-api change, preparing for expanding metadata by reed@google.com
6. quick-reject before transforming images by mtklein@chromium.org
7. convert pipe over to serial procs by reed@google.com
8. Remove SkClampRange (unused) by brianosman@google.com

Assigning it to the zmo@ for suspect CL : https://chromium.googlesource.com/chromium/src/+/ad0565be7d87893cf2d94c6a8abb78aca4553fe7


CC'ing the other components owners (reed@, vmpstr@) for their inputs

ClusterFuzz has detected this issue as fixed in range 525779:525790.

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

Fuzzer: libFuzzer_paint_op_buffer_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  target == buffers[bound_buffer_]->target in test_web_graphics_context_3d.cc
  cc::TestWebGraphicsContext3D::bufferData
  cc::TestGLES2Interface::BufferData
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=524136:524153
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=525779:525790

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

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 5219313496883200 is verified as fixed, so closing issue as verified.

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