Error while executing pdf-utils operations. Page crashed!



  • 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.



  • This error says that chrome badly crashed for unknown reasons. Unfortunately, you won't get more information and there is nothing jsreport can do for you.

    jsreport v3 is using updated chrome and that is likely the main reason you see this regression issue.

    This often happens when there are not enough memory resources, but I see you run on local so that is likely not the case.

    Are you aware of this problem with images?
    https://jsreport.net/learn/chrome-pdf#images-increasing-pdf-size



  • @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?



  • You can see the chrome number in the output logs
    0_1654272649791_upload-0d131424-23bb-4ac6-9f0f-83b9d0256558

    We were aware of some performance changes in the new chrome, but there were no other options than to update because old chrome has security holes and we need to update it regularly.


Log in to reply
 

Looks like your connection to jsreport forum was lost, please wait while we try to reconnect.