On Wed, 20 Feb 2019 19:39:39 +0000 Anton Avramov <[email protected]> wrote:
Package: chromium
Version: 72.0.3626.96-1~deb9u1
Severity: normal
Tags: upstream
Dear Maintainer,
We have many installation where chromium is started with
--remote-debugging-port=3333 so we can easy debug remotely. After an
debian package upgrade from stable 70.xxx to 72.xxx chromium cannot
start with that option and crashes imidietlly.
The same happen with --headless:
$ chromium --headless
Received signal 11 SEGV_MAPERR 000000000010
#0 0x55e9917bd711 <unknown>
#1 0x55e9917bdb7b <unknown>
#2 0x55e9917be1de <unknown>
#3 0x7f1d87d6a0e0 <unknown>
#4 0x55e9952a1891 <unknown>
#5 0x55e995296a16 <unknown>
#6 0x55e9917094fd <unknown>
#7 0x55e99172a7be <unknown>
#8 0x55e99172cd53 <unknown>
#9 0x55e99172ce80 <unknown>
#10 0x55e9917d4c62 <unknown>
#11 0x55e99175498a <unknown>
#12 0x55e98fb58ce4 <unknown>
#13 0x55e9917920a8 <unknown>
#14 0x55e9917ce154 <unknown>
#15 0x7f1d87d604a4 start_thread
#16 0x7f1d7a25cd0f clone
r8: 00007f1d677fd5f8 r9: 0000000000000001 r10: 0000000000000000 r11:
0000000000000000
r12: 000055e998e8ca30 r13: 0000000000000000 r14: 000055e995feb03e r15:
00007f1d677fd630
di: 00007f1d677fd5a0 si: 000055e996900f80 bp: 00007f1d677fd5e0 bx:
000055e998ea6270
dx: 000055e9952a1891 ax: 00007f1d677fd5a0 cx: 0000000000000096 sp:
00007f1d677fd5a0
ip: 000055e9952a1891 efl: 0000000000010206 cgf: 002b000000000033 erf:
0000000000000004
trp: 000000000000000e msk: 0000000000000000 cr2: 0000000000000010
[end of stack trace]
Calling _exit(1). Core file will not be generated.
self ref: https://phabricator.wikimedia.org/T216702
