Closed
Bug 528448
Opened 16 years ago
Closed 1 year ago
100% CPU with broken <img onerror>
Categories
(Core :: DOM: Core & HTML, defect, P3)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: fpwoshg, Unassigned)
References
Details
(Keywords: perf)
Attachments
(1 file)
|
281 bytes,
text/html
|
Details |
If the onerror attribute of an img element tries to alter the img src to point to a non-existent img Firefox uses 100% CPU until the page is closed. I found this error while browsing http://social.bioware.com/ with images disabled, the site contains the following code:
<img src="../include/js/moofacebox/images/closelabel.gif" title="close" class="facebox-close_image" onerror="this.src='../include/js/moofacebox/images/closelabel.gif'">
I have attached a reduced testcase, I'm not sure if this is considered a Firefox bug but FWIW IE8 immediately pops up a stack overflow error and does not use 100% CPU.
Tested on clean profile with:
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.3a1pre) Gecko/20091112 Minefield/3.7a1pre
Updated•16 years ago
|
OS: Windows XP → All
Hardware: x86 → All
Comment 1•13 years ago
|
||
Yeah, on IE 9, CPU's at 50% on iexplore process when testcase's open
However, FF 15.0 on Vista Basic (32-bit) doesn't use cpu 100% anymore.
Page Faults are on constant rise in small increments for the process tho.
Is that normal ?
Updated•12 years ago
|
Comment 3•11 years ago
|
||
the infinite loop also occurs when the request to the image is blocked by a firefox extension.
See this bug: https://github.com/RequestPolicy/requestpolicy/issues/441#issuecomment-51946393
Comment 4•8 years ago
|
||
https://bugzilla.mozilla.org/show_bug.cgi?id=1472046
Move all DOM bugs that haven’t been updated in more than 3 years and has no one currently assigned to P5.
If you have questions, please contact :mdaly.
Priority: -- → P5
Comment 5•3 years ago
|
||
In the process of migrating remaining bugs to the new severity system, the severity for this bug cannot be automatically determined. Please retriage this bug using the new severity system.
Severity: critical → --
Updated•3 years ago
|
Severity: -- → S3
Priority: P5 → P3
Comment 6•1 year ago
|
||
works for me. Please feel free to file a new bug.
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•