Open
Description
Attach (recommended) or Link to PDF file
N/A
Web browser and its version
Chrome 137.0.7151.55
Operating system and its version
Ubuntu
PDF.js version
5.3.31
Is the bug present in the latest PDF.js version?
Yes
Is a browser extension
No
Steps to reproduce the problem
- Run the integration tests on the bots.
- From time to time Chrome crashes (seemingly during shutdown). For example, in http://54.241.84.105:8877/b777e86d3563766/output.txt from Update dependencies and translations to the most recent versions #19997 the following is logged:
Received signal 6
#0 0x55d4dae6f1ca (/home/ubuntu/.cache/puppeteer/chrome/linux-137.0.7151.55/chrome-linux64/chrome+0x4e8f1c9)
#1 0x55d4e0b7c134 (/home/ubuntu/.cache/puppeteer/chrome/linux-137.0.7151.55/chrome-linux64/chrome+0xab9c133)
#2 0x7fc71bbb7420 (/lib/x86_64-linux-gnu/libpthread-2.31.so+0x1441f)
#3 0x55d4dc56b33b (/home/ubuntu/.cache/puppeteer/chrome/linux-137.0.7151.55/chrome-linux64/chrome+0x658b33a)
#4 0x55d4dc56a1a6 (/home/ubuntu/.cache/puppeteer/chrome/linux-137.0.7151.55/chrome-linux64/chrome+0x658a1a5)
#5 0x55d4dc569e5e (/home/ubuntu/.cache/puppeteer/chrome/linux-137.0.7151.55/chrome-linux64/chrome+0x6589e5d)
#6 0x55d4dcf29ea3 (/home/ubuntu/.cache/puppeteer/chrome/linux-137.0.7151.55/chrome-linux64/chrome+0x6f49ea2)
#7 0x55d4dcf2a61f (/home/ubuntu/.cache/puppeteer/chrome/linux-137.0.7151.55/chrome-linux64/chrome+0x6f4a61e)
#8 0x55d4dcf296a6 (/home/ubuntu/.cache/puppeteer/chrome/linux-137.0.7151.55/chrome-linux64/chrome+0x6f496a5)
#9 0x55d4dcf29541 (/home/ubuntu/.cache/puppeteer/chrome/linux-137.0.7151.55/chrome-linux64/chrome+0x6f49540)
#10 0x55d4dcf294fe (/home/ubuntu/.cache/puppeteer/chrome/linux-137.0.7151.55/chrome-linux64/chrome+0x6f494fd)
#11 0x55d4dc80df48 (/home/ubuntu/.cache/puppeteer/chrome/linux-137.0.7151.55/chrome-linux64/chrome+0x682df47)
#12 0x55d4dc80d7f5 (/home/ubuntu/.cache/puppeteer/chrome/linux-137.0.7151.55/chrome-linux64/chrome+0x682d7f4)
#13 0x55d4d8e6317f (/home/ubuntu/.cache/puppeteer/chrome/linux-137.0.7151.55/chrome-linux64/chrome+0x2e8317e)
#14 0x55d4d8e603cb (/home/ubuntu/.cache/puppeteer/chrome/linux-137.0.7151.55/chrome-linux64/chrome+0x2e803ca)
#15 0x7fc71bacb17d (/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6400.6+0x5217c)
#16 0x126c0000c600 <unknown>
#17 0x55d4d9e4858b (/home/ubuntu/.cache/puppeteer/chrome/linux-137.0.7151.55/chrome-linux64/chrome+0x3e6858a)
#18 0x55d4d9e47b28 (/home/ubuntu/.cache/puppeteer/chrome/linux-137.0.7151.55/chrome-linux64/chrome+0x3e67b27)
#19 0x55d4d9e4de68 (/home/ubuntu/.cache/puppeteer/chrome/linux-137.0.7151.55/chrome-linux64/chrome+0x3e6de67)
#20 0x55d4da3de4b6 (/home/ubuntu/.cache/puppeteer/chrome/linux-137.0.7151.55/chrome-linux64/chrome+0x43fe4b5)
#21 0x55d4db9b75e7 (/home/ubuntu/.cache/puppeteer/chrome/linux-137.0.7151.55/chrome-linux64/chrome+0x59d75e6)
#22 0x55d4db9b6c5f (/home/ubuntu/.cache/puppeteer/chrome/linux-137.0.7151.55/chrome-linux64/chrome+0x59d6c5e)
#23 0x7fc71acbc083 (/lib/x86_64-linux-gnu/libc-2.31.so+0x24082)
r8: 0000000000000000 r9: 00007ffe80f4fe20 r10: 0000000000000008 r11: 0000000000000246
r12: 0000126c008bdb18 r13: 0000126c008bdb58 r14: 000055d4d792f5c2 r15: 0000126c008a1000
di: 0000000000000002 si: 00007ffe80f4fe20 bp: 00007ffe80f50090 bx: 00007fc719ae6500
dx: 0000000000000000 ax: 0000000000000000 cx: 00007fc71acdb00b sp: 00007ffe80f4fe20
ip: 00007fc71acdb00b efl: 0000000000000246 cgf: 002b000000000033 erf: 0000000000000000
trp: 0000000000000000 msk: 0000000000000000 cr2: 0000000000000000
[end of stack trace]
- Notice that in Update dependencies and translations to the most recent versions #19997 no "success" message is posted. That's because the Crashpad process kept running and had to be killed manually.
What is the expected behavior?
The "success" message is posted.
What went wrong?
The "success" message is not posted.
Link to a viewer
No response
Additional context
In a number of previous bot hangs we have found that the Crashpad process kept running, so getting that fixed should reduce the number of hangs we experience.