undetermined progressmeter uses 100% cpu

RESOLVED WORKSFORME

Status

()

Core
Widget
--
major
RESOLVED WORKSFORME
10 years ago
5 years ago

People

(Reporter: William Vanderpol, Unassigned)

Tracking

unspecified
Points:
---
Bug Flags:
blocking1.9.1 -

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

259 bytes, application/vnd.mozilla.xul+xml
Details
(Reporter)

Description

10 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.6) Gecko/2009011913 Firefox/3.0.6
Build Identifier: XulRunner 1.8-1.9.*

when an undetermined progressmeter is active and an iframe is used in the same document, cpu usage spikes to 100% on the system and remains there until the document is closed. 

Reproducible: Always

Steps to Reproduce:
1. Load the test case in firefox / thunderbird / xulrunner.



This could be used as a type of denial of service attack?
(Reporter)

Comment 1

10 years ago
Created attachment 361759 [details]
Test case of cpu usage problem
(Reporter)

Updated

10 years ago
Summary: undetermined progress uses 100% cpu → undetermined progressmeter uses 100% cpu
(Reporter)

Updated

10 years ago
Flags: blocking1.9.1?
Flags: blocking1.9.0.7?
This needs to be confirmed and work started before we'd consider it for the 1.9.0 branch.
Flags: blocking1.9.0.7?
Not denial of service; the browser is still responsive.  On the 3.1 nightly, I get around 9% CPU usage under win32 running the test case, so this could be something related to an odd video driver and/or an odd theme.
Flags: blocking1.9.1? → blocking1.9.1-
(Reporter)

Comment 4

6 years ago
This has been fixed at some point between 1.8 and 15. Resolved
Status: UNCONFIRMED → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → WORKSFORME

Comment 5

5 years ago
I see this problem with the latest release (19.0) but only under Windows XP.  Windows 7 machines are fine.
You need to log in before you can comment on or make changes to this bug.