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. 

I'm attaching the crash output with options --remote-debugging-port=2222 and 
--debug



-- System Information:
Debian Release: 9.8
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-8-amd64 (SMP w/2 CPU cores)
Locale: LANG=bg_BG.UTF-8, LC_CTYPE=bg_BG.UTF-8 (charmap=UTF-8), 
LANGUAGE=bg_BG.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages chromium depends on:
ii  libasound2           1.1.3-5
ii  libatk1.0-0          2.22.0-1
ii  libatomic1           6.3.0-18+deb9u1
ii  libatspi2.0-0        2.22.0-6+deb9u1
ii  libavcodec57         7:3.2.12-1~deb9u1
ii  libavformat57        7:3.2.12-1~deb9u1
ii  libavutil55          7:3.2.12-1~deb9u1
ii  libc6                2.24-11+deb9u4
ii  libcairo2            1.14.8-1
ii  libcups2             2.2.1-8+deb9u3
ii  libdbus-1-3          1.10.26-0+deb9u1
ii  libdrm2              2.4.74-1
ii  libevent-2.0-5       2.0.21-stable-3
ii  libexpat1            2.2.0-2+deb9u1
ii  libflac8             1.3.2-1
ii  libfontconfig1       2.11.0-6.7+b1
ii  libfreetype6         2.6.3-3.2
ii  libgcc1              1:6.3.0-18+deb9u1
ii  libgdk-pixbuf2.0-0   2.36.5-2+deb9u2
ii  libglib2.0-0         2.50.3-2
ii  libgtk2.0-0          2.24.31-2
ii  libicu57             57.1-6+deb9u2
ii  libjpeg62-turbo      1:1.5.1-2
ii  libminizip1          1.1-8+b1
ii  libnspr4             2:4.12-6
ii  libnss3              2:3.26.2-1.1+deb9u1
ii  libopenjp2-7         2.1.2-1.1+deb9u2
ii  libopus0             1.2~alpha2-1
ii  libpango-1.0-0       1.40.5-1
ii  libpangocairo-1.0-0  1.40.5-1
ii  libpangoft2-1.0-0    1.40.5-1
ii  libpci3              1:3.5.2-1
ii  libpng16-16          1.6.28-1
ii  libpulse0            10.0-1+deb9u1
ii  libre2-3             20170101+dfsg-1
ii  libsnappy1v5         1.1.3-3
ii  libstdc++6           6.3.0-18+deb9u1
ii  libvpx4              1.6.1-3+deb9u1
ii  libwebp6             0.5.2-1
ii  libwebpdemux2        0.5.2-1
ii  libwebpmux2          0.5.2-1
ii  libx11-6             2:1.6.4-3+deb9u1
ii  libx11-xcb1          2:1.6.4-3+deb9u1
ii  libxcb1              1.12-1
ii  libxcomposite1       1:0.4.4-2
ii  libxcursor1          1:1.1.14-1+deb9u2
ii  libxdamage1          1:1.1.4-2+b3
ii  libxext6             2:1.3.3-1+b2
ii  libxfixes3           1:5.0.3-1
ii  libxi6               2:1.7.9-1
ii  libxml2              2.9.4+dfsg1-2.2+deb9u2
ii  libxrandr2           2:1.5.1-1
ii  libxrender1          1:0.9.10-1
ii  libxslt1.1           1.1.29-2.1
ii  libxss1              1:1.2.2-1
ii  libxtst6             2:1.2.3-1
ii  x11-utils            7.7+3+b1
ii  xdg-utils            1.1.1-1+deb9u1
ii  zlib1g               1:1.2.8.dfsg-5

Versions of packages chromium recommends:
ii  fonts-liberation  1:1.07.4-2
ii  libgl1-mesa-dri   13.0.6-1+b2

Versions of packages chromium suggests:
pn  chromium-driver    <none>
pn  chromium-l10n      <none>
pn  chromium-shell     <none>
pn  chromium-widevine  <none>

-- no debconf information
ATTENTION: default value of option force_s3tc_enable overridden by environment.
[15311:15311:0220/193123.276252:ERROR:sandbox_linux.cc(364)] 
InitializeSandbox() called with multiple threads in process gpu-process.
[15270:15495:0220/193123.291391:ERROR:bus.cc(396)] Failed to connect to the 
bus: Could not parse server address: Unknown address type (examples of valid 
types are "tcp" and on UNIX "unix")
Received signal 11 SEGV_MAPERR 000000000080
#0 0x55f5b8833711 <unknown>
#1 0x55f5b8833b7b <unknown>
#2 0x55f5b88341de <unknown>
#3 0x7fd81cff00e0 <unknown>
#4 0x55f5b6c1b314 <unknown>
#5 0x55f5b6c261b7 <unknown>
#6 0x55f5ba3a8634 <unknown>
#7 0x55f5b82ebf7f <unknown>
#8 0x55f5b83234cc <unknown>
#9 0x55f5b83235ee <unknown>
#10 0x55f5b83343d3 <unknown>
#11 0x55f5b8334e55 <unknown>
#12 0x55f5b6bb7fd3 <unknown>
#13 0x55f5b7031c32 <unknown>
#14 0x55f5b6bba089 <unknown>
#15 0x55f5b6bbb039 <unknown>
#16 0x55f5b6ba75be <unknown>
#17 0x55f5b82de298 <unknown>
#18 0x55f5b82de501 <unknown>
#19 0x55f5b82de8b0 <unknown>
#20 0x55f5b82e9b7a <unknown>
#21 0x55f5b82dc6c5 <unknown>
#22 0x55f5b5f84d39 ChromeMain
#23 0x7fd80f41a2e1 __libc_start_main
#24 0x55f5b5f84b8a _start
  r8: 0000000000000003  r9: 3865343834612f72 r10: 2d326232342d3465 r11: 
3361382d37366634
 r12: 00007ffe1cdda4d0 r13: 000055f5c031f2c0 r14: 00007ffe1cdda520 r15: 
000055f5c031eae0
  di: 00007ffe1cdda4d0  si: 000055f5bd3cb770  bp: 00007ffe1cdda570  bx: 
000055f5c031ebe0
  dx: 000055f5b6c1b314  ax: 00007ffe1cdda4d0  cx: 0000000000000319  sp: 
00007ffe1cdda470
  ip: 000055f5b6c1b314 efl: 0000000000010206 cgf: 002b000000000033 erf: 
0000000000000004
 trp: 000000000000000e msk: 0000000000000000 cr2: 0000000000000080
[end of stack trace]
Calling _exit(1). Core file will not be generated.

Reply via email to