Closed
Bug 603294
Opened 14 years ago
Closed 14 years ago
Firefox hangs 100% cpu during page refresh with certain content (example given)
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: jonty_lawson, Unassigned)
References
()
Details
Attachments
(3 files)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US) AppleWebKit/534.3 (KHTML, like Gecko) Chrome/6.0.472.63 Safari/534.3 Build Identifier: 3.6.10 One of the Firefox threads goes into an infinite loop during reload of certain video content displayed using flash. Note that it is a firefox thread that hangs, not the plugin container. Reproducible: Always Steps to Reproduce: 1.Load the given example page then refresh it with ctrl-f5 2. 3. Actual Results: One of the firefox threads loops infinitely Attached is the test page used. It was extracted from failblog.org and is typical of their page content (with all extraneous stuff removed). Note that the fact that there are two objects on the page seems to be important. Refreshing this page with ctrl-f5 hits the problem every time on my system. With the original failblog.org page it is more variable (probably because the content varies) and also occurs when clicking on refresh tab. Also attached is configuration information on plugins and extensions.
Comment 4•14 years ago
|
||
The Testcase is working fine here with Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.2.11) Gecko/20101001 Firefox/3.6.11 and Adobe Flash 10.2.161.23, even if I start playing both Videos before reloading them. Is the Issue reproduceable in Safe-Mode/extension-less? Is that the only Site you experienced the Issue?
Severity: major → normal
Version: unspecified → 3.6 Branch
Comment 5•14 years ago
|
||
no crash with Seamonkey trunk and Flash 10.1 r85
OK, I have been through the extensions disabling dance and it turns out to be an interaction with Firebug, but specifically version 1.3.3 For some reason the automatic update of Firebug wasn't working, and when I asked for a manual update it gave an error. I have now installed the latest version (1.5.4) and this problem no longer occurs. Thanks for the help and sorry to have failed to spot the Firebug interaction before posting the bug report. I have set the status to "resolved/invalid".
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•