Predator results and CL did not provide any possible suspects.
Using Code Search for the file, "pdf_jpx_fuzzer" assigning to the concern owner.
Suspecting Commit#
https://pdfium.git.corp.google.com/pdfium.git/+/43c8a6adc0045c974fb1c831deeef53fa5a38a82

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

libopenjpeg madness of allowing huge memory allocations, not much we can do.

ClusterFuzz testcase 4906574004092928 is still reproducing on tip-of-tree build (trunk).

If this testcase was not reproducible locally or unworkable, ignore this notification and we will file another bug soon with hopefully a better and workable testcase.

Otherwise, if this is not intended to be fixed (e.g. this is an intentional crash), please add ClusterFuzz-Ignore label to prevent future bug filing with similar crash stacktrace.