Bug#979443: chromium: desktop GUI locks up as Xorg process goes to 100%

2021-01-11 Thread Steve A.
After three full days of use, the desktop has not frozen again, and the 
Xorg process has remained below 7% CPU use.  Should I modify the menu to 
include the alternate launch command, or is there a beta version of 
chromium you would like me to try?


Steve


Steve A. wrote on 1/8/21 6:32 AM:
Thanks, Jan.  I killed chromium, upgraded to 87* again, and re-launched 
with the recommended command last night.  The user is back on this 
morning and I'm monitoring from another machine.


Steve


Jan Luca Naumann wrote on 1/7/21 2:30 AM:

Dear Steve,

with the upgrade to 87.* we included the ANGLE library which manages the
OpenGL access of chromium. Maybe this is the cause of your problem.

Could you try to launch "$ chromium --use-gl=desktop"? This should
disable the usage of ANGLE.

Best,
Jan





Bug#979443: chromium: desktop GUI locks up as Xorg process goes to 100%

2021-01-08 Thread Steve A.
Thanks, Jan.  I killed chromium, upgraded to 87* again, and re-launched 
with the recommended command last night.  The user is back on this 
morning and I'm monitoring from another machine.


Steve


Jan Luca Naumann wrote on 1/7/21 2:30 AM:

Dear Steve,

with the upgrade to 87.* we included the ANGLE library which manages the
OpenGL access of chromium. Maybe this is the cause of your problem.

Could you try to launch "$ chromium --use-gl=desktop"? This should
disable the usage of ANGLE.

Best,
Jan





Bug#979443: chromium: desktop GUI locks up as Xorg process goes to 100%

2021-01-06 Thread Steve A.

Package: chromium
Version: 87.0.4280.88-0.4~deb10u1
Severity: grave
Tags: a11y
Justification: renders package unusable

Dear Maintainer,

Subsequent to an upgrade from 83.0.4103.116-1~deb10u3 to 
87.0.4280.88-0.4~deb10u1, the desktop GUI randomly freezes, including 
the clock.  This occurred three times over the course of two days. 
Doing a ssh from another machine, and then running top, showed the Xorg 
process pegged at 100%.  Killing just the chromium process did not 
resolve the locking problem, and the only way to recover was to kill all 
processes for the GUI user.  Chromium was rolled back to 
83.0.4103.116-1~deb10u3 and there have been no freezes in over two days.



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

Kernel: Linux 4.19.0-13-amd64 (SMP w/16 CPU cores)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)

Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages chromium depends on:
ii  chromium-common  87.0.4280.88-0.4~deb10u1
ii  libasound2   1.1.8-1
ii  libatk-bridge2.0-0   2.30.0-5
ii  libatk1.0-0  2.30.0-2
ii  libatspi2.0-02.30.0-7
ii  libavcodec58 7:4.1.6-1~deb10u1
ii  libavformat587:4.1.6-1~deb10u1
ii  libavutil56  7:4.1.6-1~deb10u1
ii  libc62.28-10
ii  libcairo21.16.0-4
ii  libcups2 2.2.10-6+deb10u4
ii  libdbus-1-3  1.12.20-0+deb10u1
ii  libdrm2  2.4.97-1
ii  libevent-2.1-6   2.1.8-stable-4
ii  libexpat12.2.6-2+deb10u1
ii  libflac8 1.3.2-3
ii  libfontconfig1   2.13.1-2
ii  libfreetype6 2.9.1-3+deb10u2
ii  libgbm1  18.3.6-2+deb10u1
ii  libgcc1  1:8.3.0-6
ii  libgdk-pixbuf2.0-0   2.38.1+dfsg-1
ii  libglib2.0-0 2.58.3-2+deb10u2
ii  libgtk-3-0   3.24.5-1
ii  libharfbuzz0b2.3.1-1
ii  libicu63 63.1-6+deb10u1
ii  libjpeg62-turbo  1:1.5.2-2+deb10u1
ii  libjsoncpp1  1.7.4-3
ii  liblcms2-2   2.9-3
ii  libminizip1  1.1-8+b1
ii  libnspr4 2:4.20-1
ii  libnss3  2:3.42.1-1+deb10u3
ii  libopenjp2-7 2.3.0-2+deb10u1
ii  libopus0 1.3-1
ii  libpango-1.0-0   1.42.4-8~deb10u1
ii  libpangocairo-1.0-0  1.42.4-8~deb10u1
ii  libpng16-16  1.6.36-6
ii  libpulse012.2-4+deb10u1
ii  libre2-5 20190101+dfsg-2
ii  libsnappy1v5 1.1.7-1
ii  libstdc++6   8.3.0-6
ii  libvpx5  1.7.0-3+deb10u1
ii  libwebp6 0.6.1-2
ii  libwebpdemux20.6.1-2
ii  libwebpmux3  0.6.1-2
ii  libx11-6 2:1.6.7-1+deb10u1
ii  libx11-xcb1  2:1.6.7-1+deb10u1
ii  libxcb-dri3-01.13.1-2
ii  libxcb1  1.13.1-2
ii  libxcomposite1   1:0.4.4-2
ii  libxcursor1  1:1.1.15-2
ii  libxdamage1  1:1.1.4-3+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-7+deb10u1
ii  libxrandr2   2:1.5.1-1
ii  libxrender1  1:0.9.10-1
ii  libxslt1.1   1.1.32-2.2~deb10u1
ii  libxss1  1:1.2.3-1
ii  libxtst6 2:1.2.3-1
ii  zlib1g   1:1.2.11.dfsg-1

Versions of packages chromium recommends:
ii  chromium-sandbox  87.0.4280.88-0.4~deb10u1

Versions of packages chromium suggests:
pn  chromium-driver  
pn  chromium-l10n
pn  chromium-shell   

Versions of packages chromium-common depends on:
ii  x11-utils  7.7+4
ii  xdg-utils  1.1.3-1+deb10u1

Versions of packages chromium-common recommends:
ii  chromium-sandbox87.0.4280.88-0.4~deb10u1
ii  fonts-liberation1:1.07.4-9
ii  libgl1-mesa-dri 18.3.6-2+deb10u1
ii  libu2f-udev 1.1.9-1
ii  mate-notification-daemon [notification-daemon]  1.20.2-1
ii  notification-daemon 3.20.0-4
ii  upower  0.99.10-1

Versions of packages chromium-sandbox depends on:
ii  libc6  2.28-10

-- no debconf information