On #14303, I shared unmodified files from our bug tracker corpus that appeared to cause some problems for pdf.js.  On this issue, I'll attach files that are freshly fuzzed using files from that corpus as seeds.  I avoided files used in #14303 as seeds for these runs  

I haven't done root cause analysis, and I apologize if these are all just triggering the same underlying bug (or that fixed in #14304).  The files are named for their seed file and then the sha-256 of the fuzzed version.

[new-nasties.zip](https://github.com/mozilla/pdf.js/files/7598083/new-nasties.zip)
const loadingTask = getDocument(filename);
      loadingTasks.push(loadingTask);
      const pdf = await loadingTask.promise;
      const page = await pdf.getPage(1);
      const viewport = page.getViewport({ scale: 1.2 });
      const canvasAndCtx = CanvasFactory.create(
        viewport.width,
        viewport.height
      );
      const renderTask = page.render({
        canvasContext: canvasAndCtx.context,
        canvasFactory: CanvasFactory,
        viewport,
      });
      await renderTask.promise;
      const data = canvasAndCtx.canvas.toDataURL();
      CanvasFactory.destroy(canvasAndCtx);
      return data;
    }
    afterEach(async function () {
      // Issue 6205 reported an issue with font rendering, so clear the loaded
      // fonts so that we can see whether loading PDFs in parallel does not
      // cause any issues with the rendered fonts.
      const destrongTask) {