--- Please enter the report below this line. ---

It is well known that iceweasel / firefox often fully uses one CPU core
when a page is being displayed (see all the bug reports here and
upstream). I am used to it. However, recently, I see it fully use a CPU
core and continuing to do so, even when I close all tabs or close it.
To reproduce: Start iceweasel, open some pages, wait for some time
uintil it starts fully using a CPU core, then close all tabs. It still
fully uses a core. When I close it (using the 'x' from the window
manager), the process still fully uses a core. Sending a TERM signal
using kill works though.

Debian Release: 8.0
  500 unstable        ftp.de.debian.org
  500 testing         ftp.de.debian.org
    1 experimental    ftp.de.debian.org
--- Package information. ---
Depends                               (Version) | Installed
===============================================-+-===================
libasound2                          (>= 1.0.16) |
libatk1.0-0                         (>= 1.12.4) |
libc6                                 (>= 2.17) |
libcairo2                            (>= 1.2.4) |
libdbus-1-3                          (>= 1.0.2) |
libdbus-glib-1-2                      (>= 0.78) |
libevent-2.0-5               (>= 2.0.10-stable) |
libffi6                              (>= 3.0.4) |
libfontconfig1                        (>= 2.11) |
libfreetype6                         (>= 2.2.1) |
libgcc1                            (>= 1:4.1.1) |
libgdk-pixbuf2.0-0                  (>= 2.22.0) |
libglib2.0-0                        (>= 2.37.3) |
libgtk2.0-0                         (>= 2.24.0) |
libhunspell-1.3-0                    (>= 1.3.3) |
libnspr4                          (>= 2:4.10.3) |
libnss3                             (>= 2:3.16) |
libpango-1.0-0                      (>= 1.14.0) |
libsqlite3-0                     (>= 3.7.12-1~) |
libstartup-notification0               (>= 0.8) |
libstdc++6                             (>= 4.9) |
libvpx1                              (>= 1.3.0) |
libx11-6                                        |
libxext6                                        |
libxrender1                                     |
libxt6                                          |
zlib1g                             (>= 1:1.2.0) |
fontconfig                                      |
procps                                          |
debianutils                           (>= 1.16) |


Package's Recommends field is empty.

Suggests                   (Version) | Installed
====================================-+-===========
fonts-stix                           | 1.1.1-1
 OR otf-stix                         |
fonts-oflb-asana-math                | 000.907-6
fonts-mathjax                        |
mozplugger                           |
libgssapi-krb5-2                     | 1.12.1+dfsg-19
 OR libkrb53                         |
libgnomeui-0                         | 2.24.5-3
libcanberra0                         | 0.30-2.1

--- Output from package bug script ---

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
	 Scrolling on websites like Stackoverflow and googlemaps leads to 100% Xorg CPU usage as htop indicates:
	 USER: 'root' CPU: '98%' Command: '/usr/bin/X :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch'
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
		 Open iceweasel, visiting one of the above websites and scroll on
		 the page spikes the CPU to 100%. Tried the workaround of disable
		 the 'use hardware acceleration when available' option as proposed here:
http://unix.stackexchange.com/questions/26234/why-does-stackoverflow-in-iceweasel-cause-high-cpu-usage-for-xorg
		 but no difference. With Chromium CPU usage is less than 10%.
   * What was the outcome of this action?
	 Browser almost unusable for certain pages.
   * What outcome did you expect instead?
	 Amount of CPU usage the machine can handle.

*** End of the template - remove these template lines ***

src:iceweasel has been superseded by src:firefox-esr in version
45.0esr-1 in March 2016. Transitional packages to ease upgrades were
provided in the wheezy, jessie, stretch and buster releases. The
transitional packages have been removed finally before the bullseye
release in August 2021.
After regular security support for buster ended in August 2022 and LTS
support ended in June 2024, I'm closing the remaining bug reports now.

Andreas