chromium browser timeout when trying to download PDF/PNGs

We are trying to use some Looker features that utilize the chromium-browser, like downloading a PDF or PNG. However, when we choose to download something, a chromium-browser process starts to render the PDF, and the process never finishes.

When we show the process-list, with hierarchy, we can see the processes running (they have --type=renderer) but it always times out. See below:

root@d78a8793f6e7:/# ps aux -He
USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
root     22282  0.0  0.0  18644  3424 pts/1    Ss+  19:02   0:00 bash
root     19357  0.0  0.0  18632  3488 pts/0    Ss   18:41   0:00 bash
root     30647  0.0  0.0  34408  2888 pts/0    R+   19:57   0:00   ps aux -He
root         1  0.8  0.0  55268 20192 ?        Ss   May17  11:09 /usr/bin/python /usr/local/bin/supervisord -c /supervisord.conf
root         8  0.0  0.0   4632   792 ?        S    May17   0:00   /bin/sh /looker-start.sh
root        10  0.0  0.0   4632  1712 ?        S    May17   0:00     /bin/sh /looker_java1.8 start
root        44  120 66.4 47103724 43241756 ?   Sl   May17 1535:02       java -XX:+UseG1GC -XX:MaxGCPauseMillis=2000 -XX:MaxMetaspaceSize=800m -Xms39029899k -Xmx39029899k -verbose:gc -XX:+PrintGCD
root     27582  0.0  0.1 1679116 91436 ?       Sl   19:36   0:00         /usr/lib/chromium-browser/chromium-browser --enable-pinch --no-sandbox --remote-debugging-port=40243 --headless --hide-scr
root     27589  0.0  0.0 417396 50796 ?        S    19:36   0:00           /usr/lib/chromium-browser/chromium-browser --type=zygote --no-zygote-sandbox --no-sandbox --headless --force-device-scal
root     27606  0.0  0.0 1641032 57356 ?       Sl   19:36   0:00             /usr/lib/chromium-browser/chromium-browser --type=gpu-process --no-sandbox --disable-logging --headless --ozone-platfo
root     27590  0.0  0.0 417400 50648 ?        S    19:36   0:00           /usr/lib/chromium-browser/chromium-browser --type=zygote --no-sandbox --headless --force-device-scale-factor=1 --headles
root     27608  0.0  0.1 26748176 67832 ?      Sl   19:36   0:00             /usr/lib/chromium-browser/chromium-browser --type=renderer --headless --lang=en-US --no-sandbox --disable-logging --fo
root     27683  0.0  0.1 26959688 120444 ?     Sl   19:36   0:01             /usr/lib/chromium-browser/chromium-browser --type=renderer --headless --no-sandbox --disable-logging --force-device-sc
root     27607  0.0  0.1 1011564 67408 ?       Sl   19:36   0:00           /usr/lib/chromium-browser/chromium-browser --type=utility --utility-sub-type=network.mojom.NetworkService --lang=en-US -
root     28051  0.0  0.1 1612168 89216 ?       Sl   19:38   0:00         /usr/lib/chromium-browser/chromium-browser --enable-pinch --no-sandbox --remote-debugging-port=40237 --headless --hide-scr
root     28058  0.0  0.0 417396 50512 ?        S    19:38   0:00           /usr/lib/chromium-browser/chromium-browser --type=zygote --no-zygote-sandbox --no-sandbox --headless --force-device-scal
root     28074  0.0  0.0 1567336 57776 ?       Sl   19:38   0:00             /usr/lib/chromium-browser/chromium-browser --type=gpu-process --no-sandbox --disable-logging --headless --ozone-platfo
root     28059  0.0  0.0 417400 50800 ?        S    19:38   0:00           /usr/lib/chromium-browser/chromium-browser --type=zygote --no-sandbox --headless --force-device-scale-factor=1 --headles
root     28076  0.0  0.1 26748144 67688 ?      Sl   19:38   0:00             /usr/lib/chromium-browser/chromium-browser --type=renderer --headless --lang=en-US --no-sandbox --disable-logging --fo
root     28142  0.0  0.1 26959416 118628 ?     Sl   19:38   0:00             /usr/lib/chromium-browser/chromium-browser --type=renderer --headless --no-sandbox --disable-logging --force-device-sc
root     28075  0.0  0.1 1011564 65396 ?       Sl   19:38   0:00           /usr/lib/chromium-browser/chromium-browser --type=utility --utility-sub-type=network.mojom.NetworkService --lang=en-US -

The one kernel of relevant information we were able to find was in dpkg.log from last week where it looks like Looker automatically tried to update chromium. We are unsure if these logs resemble a successful load, but we are pretty sure this is when the problems started happening.

./dpkg.log:2022-05-09 20:21:57 install chromium-codecs-ffmpeg-extra:amd64 <none> 100.0.4896.127-0ubuntu0.18.04.1
./dpkg.log:2022-05-09 20:21:57 status half-installed chromium-codecs-ffmpeg-extra:amd64 100.0.4896.127-0ubuntu0.18.04.1
./dpkg.log:2022-05-09 20:21:57 status unpacked chromium-codecs-ffmpeg-extra:amd64 100.0.4896.127-0ubuntu0.18.04.1
./dpkg.log:2022-05-09 20:21:57 status unpacked chromium-codecs-ffmpeg-extra:amd64 100.0.4896.127-0ubuntu0.18.04.1
./dpkg.log:2022-05-09 20:21:57 install chromium-browser:amd64 <none> 100.0.4896.127-0ubuntu0.18.04.1
./dpkg.log:2022-05-09 20:21:57 status half-installed chromium-browser:amd64 100.0.4896.127-0ubuntu0.18.04.1
./dpkg.log:2022-05-09 20:22:02 status unpacked chromium-browser:amd64 100.0.4896.127-0ubuntu0.18.04.1
./dpkg.log:2022-05-09 20:22:02 status unpacked chromium-browser:amd64 100.0.4896.127-0ubuntu0.18.04.1
./dpkg.log:2022-05-09 20:22:02 install chromium-browser-l10n:all <none> 100.0.4896.127-0ubuntu0.18.04.1
./dpkg.log:2022-05-09 20:22:02 status half-installed chromium-browser-l10n:all 100.0.4896.127-0ubuntu0.18.04.1
./dpkg.log:2022-05-09 20:22:03 status unpacked chromium-browser-l10n:all 100.0.4896.127-0ubuntu0.18.04.1
./dpkg.log:2022-05-09 20:22:03 status unpacked chromium-browser-l10n:all 100.0.4896.127-0ubuntu0.18.04.1
./dpkg.log:2022-05-09 20:22:04 configure chromium-codecs-ffmpeg-extra:amd64 100.0.4896.127-0ubuntu0.18.04.1 <none>
./dpkg.log:2022-05-09 20:22:04 status unpacked chromium-codecs-ffmpeg-extra:amd64 100.0.4896.127-0ubuntu0.18.04.1
./dpkg.log:2022-05-09 20:22:04 status half-configured chromium-codecs-ffmpeg-extra:amd64 100.0.4896.127-0ubuntu0.18.04.1
./dpkg.log:2022-05-09 20:22:04 status installed chromium-codecs-ffmpeg-extra:amd64 100.0.4896.127-0ubuntu0.18.04.1
./dpkg.log:2022-05-09 20:22:04 configure chromium-browser:amd64 100.0.4896.127-0ubuntu0.18.04.1 <none>
./dpkg.log:2022-05-09 20:22:04 status unpacked chromium-browser:amd64 100.0.4896.127-0ubuntu0.18.04.1
./dpkg.log:2022-05-09 20:22:04 status unpacked chromium-browser:amd64 100.0.4896.127-0ubuntu0.18.04.1
./dpkg.log:2022-05-09 20:22:04 status unpacked chromium-browser:amd64 100.0.4896.127-0ubuntu0.18.04.1
./dpkg.log:2022-05-09 20:22:04 status unpacked chromium-browser:amd64 100.0.4896.127-0ubuntu0.18.04.1
./dpkg.log:2022-05-09 20:22:04 status half-configured chromium-browser:amd64 100.0.4896.127-0ubuntu0.18.04.1
./dpkg.log:2022-05-09 20:22:04 status installed chromium-browser:amd64 100.0.4896.127-0ubuntu0.18.04.1
./dpkg.log:2022-05-09 20:22:04 configure chromium-browser-l10n:all 100.0.4896.127-0ubuntu0.18.04.1 <none>
./dpkg.log:2022-05-09 20:22:04 status unpacked chromium-browser-l10n:all 100.0.4896.127-0ubuntu0.18.04.1
./dpkg.log:2022-05-09 20:22:04 status half-configured chromium-browser-l10n:all 100.0.4896.127-0ubuntu0.18.04.1
./dpkg.log:2022-05-09 20:22:04 status installed chromium-browser-l10n:all 100.0.4896.127-0ubuntu0.18.04.1