Protocol error (Page.printToPDF): Target closed.
-
We use docker as well.
We cannot move past version 2.4.0.
Our entire setup works using 2.4.0, but the minute that we update to 2.5.0 we get these errors.
I am not sure how we can make a replicable demo to show you. It can't be replicated in the playground.
-
@stevef51 I tried your export uploaded to dropbox and it works for me on image 2.5.0-full. I even multiplied the input data and it renders 766 pages pdf without errors. Can you try to run just the official image
jsreport/jsreport:2.5.0without any config. Upload there export you shared and run the template. Does it break for you?@AB-D It would help if you upload somewhere or email me jsreport export which is failing for you.
-
@jan_blaha
This is weird, so I changed our Azure Webapp to use "jsreport/jsreport:2.5.0-full" as you suggested and removed all custom configuration (so removed MongoDb storage etc) - it still errors with that basic 2000 record report. However running the same Docker image locally with no custom configuration (so should be exactly same as the Azure Webapp) and it runs just fine, tested up to 511 pages without an issue.Jan, Are you able to test on an Azure Webapp ?
-
@jan_blaha
Ok, its something to do with 2.5.0 and Azure Webapp - I just updated the Azure Webapp to use my hacked "2.5.0 with Chromium 64" image which is the Docker file from 2.4.0 which NPM fetches latest JsReport - and this works fine, this image however does not include the MongoDb extension (+ a bunch of other extensions) since it logs only 31 extensions found at startup whilst the "-full" images find 49 extensions
-
Yes, I confirm the behavior. It crashed on the azure web app but locally it works. We will test it with the docker image that we will ship in a few days with jsreport 2.6.0 and come back here.
-
I fixed the error "Protocol error (Page.printToPDF): Target closed." replacing 'chrome-pdf' with 'phantom-pdf'
-
Hi probably doesn't help you but I just had the same issue and downgraded to 2.4.0 to fix it. Keen to know when 2.6.0 is ready so I can test it.
-
@odirleiborgert yeah, I know that is kindof a work around but I find most reports render better with ChromePDF, although there are some instances where PhantomPDF does a better job due to rendering glitches in ChromePDF
-
Hi @jan_blaha do you have any update on this issue and version 2.6.0?
-
@bjrmatos and @jan_blaha is there any update on this issue and version 2.6.0?
-
@AB-D so far we have updated the chrome version in docker from Chrome 73 to Chrome 76, so that should solve the problem in the incoming jsreport 2.6.0, but we are going to do the release in one or two days.
-
jsreport 2.6.0 is now released with respective docker images. The newer chrome which is part of it should work better in azure web app.
