Predator and CL did not find any possible suspects.
Using Code Search for the file, "agg_rasterizer_scanline_aa.h", assigning to the concern owner who might be related.

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

ClusterFuzz has detected this issue as fixed in range 462828:462840.

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

Fuzzer: libfuzzer_pdfium_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

Crash Type: Undefined-shift
Crash Address: 
Crash State:
  bool agg::rasterizer_scanline_aa::sweep_scanline<agg::scanline_u<unsigned char> 
  void agg::render_scanlines<agg::rasterizer_scanline_aa, agg::scanline_u<unsigned
  CFX_AggDeviceDriver::RenderRasterizer
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=462808:462828
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=462828:462840

Reproducer Testcase: https://clusterfuzz.com/download/AMIfv95IM-FnDw6HtTFmzcpusPrEn7yyCxm9qSTroDKqmU_Vd4Mr4aKKX_uRtBMJc-B5Pc7pxNXQQFjUgqNs-7Yj0vWJ9jFXMIKMcIODZkzmvovB1kWx1FpzdaERCI5ngugg7xI9_2Zw2kWn_GYBbpSGgbjtkQAGMye_AfcKREZhtBJzgHmZJIijo5AY2QkQDsuw9MBmwvYnaR3Rlo8t1ssFfN9SP8OLqbQruAafrYaT6i9QgldpUXtvKl0illpj1J8n2brS2tM_GL6nbtJmbWcqLxw1YVFQ_2uzd7VKGNdy1yFnJ0kLhqPOADo3AEOzAukcJ4fWCve5um1FUCUpKpf4e5gv6CQoLVASrHQgbE1p6zQ65_6T91I?testcase_id=6608953032310784


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.

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

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

I don't see why changing to jpeg-turbo would if an issue in the text drawing path. Re-opening so we can verify if this is actually fixed.

Bulk-WontFixing these bugs. This was a bug on ClusterFuzz side, see bug 717534. We will start seeing new testcases auto-filed in a day or two. We can't leave these open as ClusterFuzz won't autoverify them after ClusterFuzz-Wrong label.

We have made a bunch of changes on ClusterFuzz side, so resetting ClusterFuzz-Wrong label.