Failed to print using chromium=128.0.6613.84-1~deb12u1 #326
Labels
bug
Something isn't working
Comments
|
For what it's worth, starting at least a week ago, my Phoenix app with chromic_pdf and headless chrome embedded won't event start up. Somehow the buildpack I am using on Gigalixir grabbed the same version of Chrome as the OP; 128.0.6613.84, and now my app won't start properly. In some cases it refuses connections on port 4000. In other cases it just restarts over and over. My logs are different than the OP, however. There's a lot of this:
I tried removing the It seems pretty clear that this is a change in Chrome and not in ChromicPDF, but maybe you can find a workaround. |
|
As a follow up. I changed the Again, this is in the Gigalixir PaaS. It's running Heroku's buildpack heroku-20 (Ubuntu 20). I also upgraded to ChromicPDF 1.17.0. And I changed to this Chrome buildpack: https://github.com/heroku/heroku-buildpack-chrome-for-testing While my app still fails at startup, the output has changed dramatically to the following: I don't know if any of that helps, but if you have any thoughts, I'm all ears. Thanks!!! |
|
A few more bits of information, if you don't mind. It appears that after I (reluctantly) turned no-sandbox on, the app does indeed startup and I can generate PDFs as before. It's just that all that ☝️ crazy stuff gets dumped into my logs first. Incidentally, I put back the call to Something changed in Chrome between versions 127 and 128 that just made everything go sideways, and I don't see any way to pin the Chrome buildpack I'm using to a certain chrome version, it's always going to pick the current stable release. 😞 |
|
Hey @petelacey. I ran into the same issue. For me, it seemed to be large images being displayed as base64 data. 127 was fine, and 128 crashed intermittently. I forked the "old" chrome buildpack and added the ability for it to read a |
|
Thanks, @metabren!!! You, sir, are a marvel. I didn't even think this was a possible. For now, I've temporarily pivoted over to a wkhtmltopdf solution (my PDF needs are modest), but I will definitely try this out next week. |
|
Hello both, thank you for the information. Unfortunately, I don't have much time to look into it further. But considering there are possibly related active issues in other repositories, this may as well be a Chromium bug and we only need to give upstream some time. @andreasknoepfle Confirmed this is an issue for Alpine-3.20 based images, see https://gist.github.com/maltoe/dcc697f17b92bb1911b74a44d534b5b9 (124 works, 128 crashes) |
|
Apologies @maltoe, I should have said. I definitely would consider this a Chromium bug. Hope they sort it out soon. |
|
We've also encountered this issue, we are using this in our Dockerfile to install a specific version: ENV CHROME_VERSION=126.0.6478.182-1
RUN apt update && apt install -y --no-install-recommends \
apt-transport-https \
ca-certificates \
curl \
fontconfig \
fonts-freefont-ttf \
fonts-ipafont-gothic \
fonts-kacst \
fonts-liberation \
fonts-noto \
fonts-roboto \
fonts-symbola \
fonts-thai-tlwg \
fonts-wqy-zenhei \
gnupg \
libatk-bridge2.0-0 \
libatspi2.0-0 \
libexif-dev \
libgbm1 \
libgl1-mesa-dri \
libgl1-mesa-glx \
libgtk-3-0 \
libu2f-udev \
libv4l-0 \
libvulkan1 \
libxkbcommon0 \
wget \
xdg-utils \
&& wget --no-check-certificate https://dl.google.com/linux/chrome/deb/pool/main/g/google-chrome-stable/google-chrome-stable_${CHROME_VERSION}_amd64.deb \
&& dpkg -i google-chrome-stable_${CHROME_VERSION}_amd64.deb \
&& apt -y -f install \
&& apt purge --auto-remove -y curl gnupg wget \
&& rm -rf /var/lib/apt/lists/* \
&& rm google-chrome-stable_${CHROME_VERSION}_amd64.deb |
|
We also had this problem. Headless printing was OK with Chromium 126, but 128 broke it. |
|
@satphil That's good news, thank you! |
|
Don't want to ruin the party, but we just tried to start our application with With |
I can't reproduce the crash with this. I get the same output, but the test.pdf is printed 🤔 |
|
@andreasknoepfle Dockerfile in gist still produces the same result for me. Errors + no PDF created. Also added another one based on Bookworm, no PDF created. Am on Linux and amd64 (Ryzen), just for reference. Unfortunately don't have much time to look into this. Still very mysterious. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hey there!!
I see nice improvements in the library! Thanks a lot!
I was releasing a new version of my app today (with Chromic 1.17) and saw that all PDF rendering started to crash..
After trying to rollback Chromic's version and seeing that it wasn't the problem, I looked at the difference between both docker images.. the chromium package's version!
I also build locally and for
128.0.6613.84-1~deb12u1, all my renders fail with the following error:Not sure if the error message helps here a lot..
Any idea why this could be happening??
Thanks in advance!!
The text was updated successfully, but these errors were encountered: