latest snap on Ubuntu LTS
ver : 84.0.4147.89
https://bugs.chromium.org/p/chromium/issues/detail?id=1106509#c2
Can you add debug symbols for libs? I'd be happy to provide a backtrace.
note, I am running with GPU disabled!
There are various SIGTRAP, SIGSEGV core dumps I can easily reproduce
Run this 50 times
chromium-browser --no-sandbox --incognito --virtual-time-budget=5000 --disable-gpu --headless --print-to-pdf=a.pdf http://www.chimpazee.jp >> log.log 2>&1
other sites easy to reproduce if you run it 50 times
Sri-Langka.com
newdress.it
cwalkerart.net
What went wrong?
Failed to open /dev/null
[0716/091926.883693:WARNING:gpu_process_host.cc(1233)] The GPU process has crashed 1 time(s)
[0716/091926.889564:WARNING:gpu_process_host.cc(1233)] The GPU process has crashed 2 time(s)
[0716/091926.893577:WARNING:gpu_process_host.cc(1233)] The GPU process has crashed 3 time(s)
[0716/091926.894491:WARNING:gpu_process_host.cc(1233)] The GPU process has crashed 4 time(s)
[0716/091926.908258:WARNING:gpu_process_host.cc(1233)] The GPU process has crashed 5 time(s)
[0716/091926.910687:WARNING:gpu_process_host.cc(1233)] The GPU process has crashed 6 time(s)
[0716/091926.910721:FATAL:gpu_data_manager_impl_private.cc(439)] GPU process isn't usable. Goodbye.
Trace/breakpoint trap
other core dumps from this release
Chrome_IOThread_S5_1594714909.core
Chrome_IOThread_S5_1594716342.core
Chrome_IOThread_S5_1594716369.core
Chrome_IOThread_S5_1594716698.core
Chrome_IOThread_S5_1594719025.core
Chrome_IOThread_S5_1594719158.core
Chrome_IOThread_S5_1594719721.core
Chrome_IOThread_S5_1594720056.core
Chrome_IOThread_S5_1594720555.core
Chrome_IOThread_S5_1594720727.core
Chrome_IOThread_S5_1594723143.core
Chrome_IOThread_S5_1594723555.core
Chrome_IOThread_S5_1594724765.core
Chrome_IOThread_S5_1594726735.core
chrome_S5_1594713852.core
chrome_S5_1594714094.core
chrome_S5_1594715092.core
chrome_S5_1594715446.core
chrome_S5_1594716376.core
chrome_S5_1594717583.core
chrome_S5_1594718113.core
chrome_S5_1594719128.core
chrome_S5_1594719384.core
chrome_S5_1594721440.core
chrome_S5_1594721535.core
chrome_S5_1594722795.core
chrome_S5_1594722978.core
chrome_S5_1594723249.core
chrome_S5_1594724206.core
chrome_S5_1594724258.core
chrome_S5_1594724538.core
chrome_S5_1594724988.core
chrome_S5_1594725002.core
chrome_S5_1594726378.core
chrome_S6_1594713950.core
chrome_S6_1594714908.core
chrome_S6_1594716342.core
chrome_S6_1594716368.core
chrome_S6_1594716697.core
chrome_S6_1594717712.core
chrome_S6_1594719024.core
chrome_S6_1594719157.core
chrome_S6_1594719720.core
chrome_S6_1594720055.core
chrome_S6_1594720554.core
chrome_S6_1594720726.core
chrome_S6_1594720810.core
chrome_S6_1594721013.core
chrome_S6_1594722356.core
chrome_S6_1594723142.core
chrome_S6_1594723554.core
chrome_S6_1594724764.core
chrome_S6_1594726734.core
ThreadPoolForeg_S5_1594714202.core
ThreadPoolForeg_S5_1594714760.core
ThreadPoolForeg_S5_1594717626.core
ThreadPoolForeg_S5_1594720170.core
ThreadPoolForeg_S5_1594721977.core
ThreadPoolForeg_S5_1594724067.core
ThreadPoolForeg_S5_1594726574.core
ThreadPoolServi_S5_1594714496.core
ThreadPoolServi_S5_1594718153.core
ThreadPoolServi_S5_1594718433.core
ThreadPoolServi_S5_1594718656.core
ThreadPoolServi_S5_1594721429.core
ThreadPoolServi_S5_1594721635.core
ThreadPoolServi_S5_1594721840.core
ThreadPoolServi_S5_1594723905.core
ThreadPoolServi_S5_1594726588.core
ThreadPoolServi_S5_1594726621.core
See my comment on the upstream bug report: https:/ /bugs.chromium. org/p/chromium/ issues/ detail? id=1106509# c21
I'm unable to reproduce the crash locally, unfortunately. Let's keep this bug open, and continue the conversation on the upstream bug report, which has more useful data and input from upstream.