64049 - Enourmous IFRAMEs cause freeze

Status: RESOLVED FIXED

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

Description

[Brian 'netdragon' Bober]

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.

Comment 1

[Brian 'netdragon' Bober]

Attachment: Test case

Comment 2

[Håkan Waara]

As you say, this may be a problem with your memory. Thus no problem in Mozilla.

Comment 3

[Brian 'netdragon' Bober]

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). 

Comment 4

[Keyser Sose]

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. 

Comment 5

[Håkan Waara]

Still no crash for me on this bug. If you can't reproduce it in the latest
nightly, then please mark it WORKSFORME. Thanks!

Comment 6

[Brian 'netdragon' Bober]

Still crashes for me - win2k latest build.

Comment 7

[Brian 'netdragon' Bober]

Memory goes up 3 MB then boom. I can close Mozilla, but thats it.

Comment 8

[Kevin McCluskey (gone)]

Setting milestone to future.

Comment 9

[Amarendra Hanumanula]

QA Contact update

Comment 10

[Ken Snider]

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!)

Comment 11

[Kevin McCluskey (gone)]

Bulk reassignin HTML FRAME/IFRAME bugs to Eric.

Comment 12

[David Gerard]

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 ...

Comment 13

[ronald]

*** Bug 114196 has been marked as a duplicate of this bug. ***

Comment 14

[ronald]

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.

Comment 15

[Kevin McCluskey (gone)]

Taking this bug

Comment 16

[Kevin McCluskey (gone)]

Fixed by checkin for bug 114082

Comment 17

[Jesse Ruderman]

Crashtest added as part of http://hg.mozilla.org/mozilla-central/rev/5a6def05ccbc