Closed Bug 64049 Opened 25 years ago Closed 24 years ago

Enourmous IFRAMEs cause freeze

Categories

(Core :: Layout: Images, Video, and HTML Frames, defect)

defect
Not set
major

Tracking

()

RESOLVED FIXED
mozilla0.9.8

People

(Reporter: netdragon, Assigned: kmcclusk)

References

Details

(Keywords: crash, testcase)

Attachments

(1 file)

I searched for this bug and couldn't find one similiar. Tested on: Build ID: 2000122920 System: Windows NT 5 (2000) IFrames that are enormous cause Mozilla to freeze and the only button that works is the close window. Mozilla should refuse to load such a large page if the memory of the system can't support it, etc. Going to attach test case.
Attached file Test case
As you say, this may be a problem with your memory. Thus no problem in Mozilla.
It is a problem with Mozilla if it tries to use more memory than the system has. It should have a way to verify that the system will have enough memory or only load a portion of the page. My computer has plenty of memory to view all web pages (as far as I know).
This page crashes Mozilla on Linux. Platform: PC OS: Linux 2.2.16 Mozilla Build: 2000122808 M18 Trunk Build I am going to go ahead and mark new.
Severity: normal → major
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: crash, testcase
OS: Windows 2000 → All
Hardware: PC → All
Still no crash for me on this bug. If you can't reproduce it in the latest nightly, then please mark it WORKSFORME. Thanks!
Still crashes for me - win2k latest build.
Memory goes up 3 MB then boom. I can close Mozilla, but thats it.
Setting milestone to future.
Target Milestone: --- → Future
QA Contact update
QA Contact: petersen → amar
This still crashes builds as of 2001050212-Trunk - An incredibly easy DoS of Mozilla, IMHO - both IE and NS4x handle the testcase without crashing (though NS4x doesn't display anything, but at least it doesn't crash!)
Bulk reassignin HTML FRAME/IFRAME bugs to Eric.
Assignee: pollmann → evaughan
The attached test case attachment 21539 [details] doesn't crash or freeze Mozilla on 2001100708-trunk, Windows NT4sp6a, PIII-600, 320 meg memory. However, what does happen is that the throbber stops throbbing and the window in question just ... sits there. The app doesn't respond until you close the offending window. Then everything is fine. The app is not taking 100% CPU, it's taking 0%. Nothing will work until you close the offending window, but then it's all OK. So it's no longer the instant DoS it was a few months ago ...
*** Bug 114196 has been marked as a duplicate of this bug. ***
Bug 114196 was marked as a duplicate by me, since the testcases of bug 64049 show the same behaviour. The discussion in bug 114196 however, refer to the bug behaviour in the linux environment, so please see the comments in that bug for additional information on the bug.
Taking this bug
Assignee: eric → kmcclusk
Target Milestone: Future → mozilla0.9.8
Fixed by checkin for bug 114082
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Flags: in-testsuite+
Product: Core → Core Graveyard
Component: Layout: HTML Frames → Layout: Images
Product: Core Graveyard → Core
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: