@jan_blaha I'm running this locally before deploying to prod so I tried to manually allocate more memory (8GB) to the node process running jsreport but that didn't work. I haven't been able to fully resolve the issue but I did find something interesting.

I tried providing our own version of chromium by setting "executablePath": "chrome-mac-${#}/Chromium.app/Contents/MacOS/Chromium". I tried 4 versions of chromium: r706915 (jsreport 2.11.0 - puppeteer 2.0.0), r950341 (js-report 3.7.1 - puppeteer 13.1.2), r991974 (puppeteer 14.0.0) and r1036695 (puppeteer 16.1.1). Running the reports worked with all 4 except r950341.

Do you think upgrading the chromium version would fix this issue? If so, is there a plan to upgrade the puppeteer version jsreport is using in the near future? Or if there is an alternative way we can do so on our end?

@jan_blaha I have tried again on jsreport 3.7.1 but still facing the same issues. I've also tried modifying the config for chrome-pdf and its launchOptions but haven't been successful. Is there anything else you can suggest?

@jan_blaha Thank you for the prompt reply. I forgot to mention that these same reports run perfectly fine in 2.11.

I have been successful with running some similar reports that are around 5 mb in size, but that's the max. Anything larger than that fails.

I think that it is a problem with images because these certain reports contain large jpegs of maps. Resizing is not really an option for us since these maps are very detailed by design. Would there be an alternative solution or any more insight into what changed with v3.5 and the updated chrome?

Hi, I am getting the error below. I'm using jsreport v3.5.0 and node v16.15.0

Error while executing pdf-utils operations. Page crashed!
Error: Error while executing pdf-utils operations. Page crashed!
    at module.exports (/Users/user/Documents/workspace/jsreporting/node_modules/@jsreport/jsreport-core/lib/shared/createError.js:10:13)
    at WorkerReporter.createError (/Users/user/Documents/workspace/jsreporting/node_modules/@jsreport/jsreport-core/lib/shared/reporter.js:47:12)
    at AsyncFunction.<anonymous> (/Users/user/Documents/workspace/jsreporting/node_modules/@jsreport/jsreport-pdf-utils/lib/worker.js:191:22)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async ListenerCollection.fire (/Users/user/Documents/workspace/jsreporting/node_modules/@jsreport/jsreport-core/lib/shared/listenerCollection.js:157:21)
    at async afterRender (/Users/user/Documents/workspace/jsreporting/node_modules/@jsreport/jsreport-core/lib/worker/render/render.js:103:5)
    at async WorkerReporter._render (/Users/user/Documents/workspace/jsreporting/node_modules/@jsreport/jsreport-core/lib/worker/render/render.js:148:7)
    at async /Users/user/Documents/workspace/jsreporting/node_modules/@jsreport/jsreport-core/lib/worker/reporter.js:177:19
    at async Domain.<anonymous> (/Users/user/Documents/workspace/jsreporting/node_modules/@jsreport/advanced-workers/lib/workerHandler.js:141:19)
caused by: Error: Page crashed!
    at Page._onTargetCrashed (/Users/user/Documents/workspace/jsreporting/node_modules/puppeteer/lib/cjs/puppeteer/common/Page.js:325:28)
    at /Users/user/Documents/workspace/jsreporting/node_modules/puppeteer/lib/cjs/puppeteer/common/Page.js:155:57
    at /Users/user/Documents/workspace/jsreporting/node_modules/puppeteer/lib/cjs/vendor/mitt/src/index.js:51:62
    at Array.map (<anonymous>)
    at Object.emit (/Users/user/Documents/workspace/jsreporting/node_modules/puppeteer/lib/cjs/vendor/mitt/src/index.js:51:43)
    at CDPSession.emit (/Users/user/Documents/workspace/jsreporting/node_modules/puppeteer/lib/cjs/puppeteer/common/EventEmitter.js:72:22)
    at CDPSession._onMessage (/Users/user/Documents/workspace/jsreporting/node_modules/puppeteer/lib/cjs/puppeteer/common/Connection.js:249:18)
    at Connection._onMessage (/Users/user/Documents/workspace/jsreporting/node_modules/puppeteer/lib/cjs/puppeteer/common/Connection.js:117:25)
    at WebSocket.<anonymous> (/Users/user/Documents/workspace/jsreporting/node_modules/puppeteer/lib/cjs/puppeteer/node/NodeWebSocketTransport.js:13:32)
    at WebSocket.onMessage (/Users/user/Documents/workspace/jsreporting/node_modules/ws/lib/event-target.js:199:18)

I am currently testing v3.5. We use 2.11 in production and are looking into upgrading soon but I am running into this issue with large reports or those that take long to generate.

Anyone know what the issue could be? Any help is appreciated.

You have to add the property values "license": { "development": true } to your jsreport.config.json or similar file. It's explained in the v3 migration guide under "licensing development mode". https://jsreport.net/learn/v3-migration-guide

That should eliminate that message.

I've seen this code in some legacy reports' scripts in my org but I can't seem to find documentation on what it means. And yes, I did search on the jsreport site and forum but couldn't find much or anything helpful.
The code is: req.options.preview = false
I logged the options object and it's just this (before setting it to false):

"options": {
      "preview": "true"

What does preview refer to here? Thanks in advance for your help

Ah ok, yeah that will work for now. Thank you!

Just wondering if there are docs available for each jsreport version released. My team and I are using 2.4.0 and we're working on upgrading to 2.11.0 but it will take some time as we have a lot of reports running. I find myself trying to implement things I see on the site/forum but they don't work and I'm guessing it's because of the version I'm on.

I looked on github and npm but didn't find anything. Thanks in advance.