Predator did not provide any possible suspects.
Assigning to the concern owner from CL --
https://chromium.googlesource.com/chromium/src/+log/e577ed818964e9fc4dae8e30458d6c0cbef18f44..7dd8521be01b568b6b2df7ef14f9787a3def7ea5?pretty=fuller

Suspecting Commit#
https://chromium.googlesource.com/chromium/src/+/8057b67871ac67f91e0600d01cd0517c61a6ac11

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

Mmh, it looks like swiftshader has linking issues when built with is_ubsan_security = true:

(If you comment the line "logging::SetMinLogLevel(logging::LOG_FATAL);" in gpu/command_buffer/tests/fuzzer_main.cc)

[0613/105607.574291:ERROR:gl_implementation.cc(246)] Failed to load /usr/local/google/home/piman/work/chrome/src/outf_Ng/Release/swiftshader/libGLESv2.so: /usr/local/google/home/piman/work/chrome/src/outf_Ng/Release/swiftshader/libGLESv2.so: undefined symbol: _ZTIN3egl7SurfaceE


c++filt says this is "typeinfo for egl::Surface"


It looks like libGLESv2 still uses types from libEGL (e.g. egl::Surface in es2::Context::makeCurrent), but:
1- libGLESv2 doesn't link against libEGL
2- libEGL whitelists exported symbols, and this one is not exported, so it wouldn't help anyway.

Fixed by https://swiftshader-review.googlesource.com/10129
I'll wait for ClusterFuzz to confirm.

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

commit df3cf28204ad1102ca9c8d79182d46dc44011c64
Author: capn <capn@chromium.org>
Date: Sat Jun 24 00:15:49 2017

Roll SwiftShader 3b9e1ea..9282c6d

https://swiftshader.googlesource.com/SwiftShader.git/+log/3b9e1ea..9282c6d

BUG=735508
BUG= 686980 
BUG= 732667 

TEST=bots

CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.win:win_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel

Change-Id: I44ad5b4094a66e5e90bb354d9563be61d6b92623
Review-Url: https://codereview.chromium.org/2953313002
Cr-Commit-Position: refs/heads/master@{#482085}

[modify] https://crrev.com/df3cf28204ad1102ca9c8d79182d46dc44011c64/DEPS

ClusterFuzz has detected this issue as fixed in range 481528:482652.

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

Fuzzer: libFuzzer_gpu_swiftshader_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  gl::init::InitializeGLOneOffImplementation( gl::kGLImplementationSwiftShaderGL, 
  gpu::CommandBufferSetup::CommandBufferSetup
  __cxx_global_var_init
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=478714:478793
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=481528:482652

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


See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md for more information.

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