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

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

Since it is related to Swiftshader component, assigning it to capn@

capn@ could you please look into it


Thank You...

We very recently updated SwiftShader's GLSL preprocessor with ANGLE's, and the latter also has a fuzzer like this so it probably already fixed the issue. We haven't rolled DEPS to a newer revision yet though...

ClusterFuzz has detected this issue as fixed in range 529109:529113.

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

Fuzzer: libFuzzer_swiftshader_vertex_routine_fuzzer
Job Type: libfuzzer_chrome_msan
Platform Id: linux

Crash Type: Stack-overflow
Crash Address: 0x7ffc01424ff8
Crash State:
  pp::MacroExpander::collectMacroArgs
  pp::MacroExpander::expandMacro
  pp::MacroExpander::pushMacro
  
Sanitizer: memory (MSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=521502:521555
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=529109:529113

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

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

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