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)
if (isNodeJS) {
        pending("Worker is not supported in Node.js.");
      }
      const worker = new PDFWorker({ name: "test1" });
      const loadingTask = getDocument(
        buildGetDocumentParams(basicApiFileName, {
          worker,
        })
      );
      loadingTask.promise.then(function () {
        const docWorker = loadingTask._worker;
        expect(!!docWorker).toEqual(false);
        
        const messageHandlerPort = loadingTask._transport.messageHandler.comObj;
        expect(messageHandlerPort === worker.port).toEqual(true);
      });
      const destroyPromise = loadingTask.promise.then(function () {
        return loadingTask.destroy();
      });
      await destroyPromise;
      expect(worker.destroyed).toEqual(false);
      worker.destroy();
    });
    it("creates more than one worker", async function () {
      if (isNodeJS) {
        pending("Worker is not supported in Node.js.");
      }
      const worker1 = new PDFWorker({ name: "test1" });
      const worker2 = new PDFWorker({ name: "test2" });
      const worker3 = new PDFWorker({ name: "test3" });