Replies: 2 comments
-
@nbyloff Did you come up with any solution to this? I believe I am running into a similar issue on a new dev machine I just setup. Thanks! |
Beta Was this translation helpful? Give feedback.
0 replies
-
@benddailey No and I haven't had time to troubleshoot a potential solution. This user on SO solved a different solution with a chromium image. I was going to test if using this image with the correct version solved my issues. At worst, it will allow me to eliminate Chromium version being the reason it's timing out. I'll eventually test and report back, but if it works for you, please let me know. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have been using this package with puppeteer v14.4.1 for a while now in a docker container. I have noticed I am having font loading issues and the only solution that worked was base64 the font in my CSS file, but that made the PDF size explode from 3MB to 45MB.
Anyways, I am trying to upgrade to a more current version to see if I can get my fonts to load without the file size issue. I have upgraded to puppeteer v.19.7.0. ( I installed node 18.x inside the container). I am testing on a Mac M1 machine, but I run my docker container with
--platform linux/amd64
. Within the docker container, I make sure the correct chromium is installed withnode node_modules/puppeteer/install.js
.Based on the install path of chromium, I update my Browsershot PDF command:
The problem is, it hangs indefintely until it hits my timeout. On v14.4.1 this process takes less than 60 seconds so I know it's not still running. It's not giving me any additional information other than there is a timeout. Do I have any options to debug this process? I am wondering if puppeteer is spitting out any information the ProcessTimeOutException doesn't know about. If I run
ps
inside the container, I do see a chrome executable running, but not high usage when it's working normally. Just like 12% vs. 103% CPU usage.Currently I have stripped my HTML down to a single page that is not loading any external resources like JS or CSS files. Just pure HTML, and it still hangs.
$ npm --version
9.5.1
$ node --version
v18.16.1
Beta Was this translation helpful? Give feedback.
All reactions