Your message dated Sat, 22 Jul 2017 11:36:30 -0400
with message-id
<CANTw=MMPrVd4AMhbLRq0Lv3SAnn8GtnTb-13=r-xnbpx0oz...@mail.gmail.com>
and subject line re: chromium: Some web pages use 100% cpu all the time
has caused the Debian Bug report #831445,
regarding chromium: Some web pages use 100% cpu all the time
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
831445: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831445
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: chromium
Version: 51.0.2704.79-1
Severity: normal
Dear maintainer,
i've noticed some web pages, such as
http://www.nationalgeographic.com/photography/photo-of-the-day/2016/7/sri-
lanka-tree-scene/
http://www.nationalgeographic.com/photography/photo-of-the-day/2016/7/hussaini-
bridge-pakistan/
use 100% of cpu, all the time, even when the tab is hidden.
This happens with all plugins/extensions removed or not, in incognito or not.
With flashblock or not.
With adblock or not.
Under firefox, the page goes at high cpu during loading, but then goes back to
normal.
I don't know how to identify which component takes so much cpu, but it seems
strange that a "normal" web page uses 100% of a cpu thread all the time.
Best,
Ara
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.6.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.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.1-2
ii libatk1.0-0 2.20.0-1
ii libavcodec57 10:3.0-dmo4
ii libavformat57 10:3.0-dmo4
ii libavutil55 10:3.0-dmo4
ii libc6 2.23-1
ii libcairo2 1.14.6-1+b1
ii libcups2 2.1.4-4
ii libdbus-1-3 1.10.8-1
ii libexpat1 2.2.0-1
ii libfontconfig1 2.11.0-6.4
ii libfreetype6 2.6.3-3+b1
ii libgcc1 1:6.1.1-9
ii libgdk-pixbuf2.0-0 2.34.0-1
ii libglib2.0-0 2.48.1-2
ii libgnome-keyring0 3.12.0-1+b1
ii libgtk2.0-0 2.24.30-2
ii libharfbuzz0b 1.2.6-2
ii libjpeg62-turbo 1:1.5.0-1
ii libnspr4 2:4.12-2
ii libnspr4-0d 2:4.12-2
ii libnss3 2:3.23-2
ii libnss3-1d 2:3.23-2
ii libpango-1.0-0 1.40.1-1
ii libpangocairo-1.0-0 1.40.1-1
ii libpci3 1:3.3.1-1.1
ii libspeechd2 0.8.4-2
ii libstdc++6 6.1.1-9
ii libx11-6 2:1.6.3-1
ii libxcomposite1 1:0.4.4-1
ii libxcursor1 1:1.1.14-1+b1
ii libxdamage1 1:1.1.4-2+b1
ii libxext6 2:1.3.3-1
ii libxfixes3 1:5.0.2-1
ii libxi6 2:1.7.6-1
ii libxml2 2.9.3+dfsg1-1.2
ii libxrandr2 2:1.5.0-1
ii libxrender1 1:0.9.9-2
ii libxslt1.1 1.1.28-4
ii libxss1 1:1.2.2-1
ii libxtst6 2:1.2.2-1+b1
ii x11-utils 7.7+3
ii xdg-utils 1.1.1-1
Versions of packages chromium recommends:
ii fonts-liberation 1.07.4-1
Versions of packages chromium suggests:
ii chromium-l10n 51.0.2704.79-1
-- no debconf information
--- End Message ---
--- Begin Message ---
Unfortunately upstream closed this bug without doing any work. If
this is still a problem, please reopen a discussion with them.
Best wishes,
Mike
--- End Message ---
