Reply to ProtocolError: Protocol error (Page.printToPDF): Printing failed on Invalid Date

dvs0416 — Invalid Date

We are having trouble getting a text file printed (ie. no images). We are using JSREPORTONLINE on a bronze plan and getting the following error when attempting to post an 8.5MB JSON body.

Protocol error (Page.printToPDF): Printing failed
ProtocolError: Protocol error (Page.printToPDF): Printing failed
    at new Callback (/app/node_modules/puppeteer-core/lib/cjs/puppeteer/common/Connection.js:62:35)
    at CallbackRegistry.create (/app/node_modules/puppeteer-core/lib/cjs/puppeteer/common/Connection.js:108:26)
    at Connection._rawSend (/app/node_modules/puppeteer-core/lib/cjs/puppeteer/common/Connection.js:224:26)
    at CDPSessionImpl.send (/app/node_modules/puppeteer-core/lib/cjs/puppeteer/common/Connection.js:433:78)
    at CDPPage.createPDFStream (/app/node_modules/puppeteer-core/lib/cjs/puppeteer/common/Page.js:738:88)
    at CDPPage.pdf (/app/node_modules/puppeteer-core/lib/cjs/puppeteer/common/Page.js:771:37)
    at /app/node_modules/@jsreport/jsreport-chrome-pdf/lib/conversion.js:391:27
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async /app/node_modules/@jsreport/jsreport-chrome-pdf/lib/conversion.js:432:22

Smaller payloads work fine. Since this payload is much smaller than the 20MB limit, we aren't sure what is going on or how to address this.

Reply to ProtocolError: Protocol error (Page.printToPDF): Printing failed on Invalid Date

admin — Invalid Date

This means chrome badly crashed without providing further explanation.
The jsreportonline plan or actual input JSON size has no impact on this, but rather what exactly is chrome printing.

Please try to disable generating the accessibility tags
https://jsreport.net/learn/chrome-pdf#aria