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)
});
    it("gets fingerprints", function () {
      expect(pdfDocument.fingerprints).toEqual([
        "ea8b35919d6279a369e835bde778611b",
        null,
      ]);
    });
    it("gets fingerprints, from modified document", async function () {
      const loadingTask = getDocument(
        buildGetDocumentParams("annotation-tx.pdf")
      );
      const pdfDoc = await loadingTask.promise;
      expect(pdfDoc.fingerprints).toEqual([
        "3ebd77c320274649a68f10dbf3b9f882",
        "e7087346aa4b4ae0911c1f1643b57345",
      ]);
      await loadingTask.destroy();
    });
    it("gets page", async function () {
      const data = await pdfDocument.getPage(1);
      expect(data instanceof PDFPageProxy).toEqual(true);
      expect(data.pageNumber).toEqual(1);
    });
    it("gets non-existent page", async function () {
      let outOfRangePromise = pdfDocument.getPage(100);
      let nonIntegerPromise = pdfDocument.getPage(2.5);
      let nonNumberPromise = pdfDocument.getPage("1");
      outOfRangePromise = outOfRangePromise.then(
        function () {
          throw new Error("shall fail for out-of-range pageNumber parameter");