Closed Bug 122856 Opened 23 years ago Closed 23 years ago

all RAM and CPU exhausted then crash

Categories

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

defect

Tracking

()

RESOLVED DUPLICATE of bug 98158
mozilla1.1alpha

People

(Reporter: psj, Assigned: john)

References

()

Details

(Keywords: crash)

From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.7) Gecko/20011227 BuildID: 2001122709 Go to the page (via the steps below). Mozilla starts to exhaust RAM while the page loads until it crashes (256+Mb on this PC). Reproducible: Always Steps to Reproduce: 1. go to http://www.english-heritage.org.uk/ 2. accept the cookie always (not required?) 3. click on the "Terms and Conditions" link at the bottom of the page Actual Results: Mozilla goes into the "loading" state and states to consume more and more memory. Eventually all available memory is exhausted (and no page is loaded). Expected Results: The page should load and be displayed without a lot of memory being used.
I have confirmed that this still occurs under mozilla 0.9.8 (Red Hat 7.2, mozilla RPMs).
confirming on moz 0.9.8 on Win2k ! set confirmed and os = all ?
Looks like another case of recursive frames. Suspect dup of bug 89300.
Assignee: asa → jkeiser
Component: Browser-General → HTMLFrames
QA Contact: doronr → amar
I confirm this in build 2002022108 on Mac OS X. (although I never did crash since I have a gig of ram on this puppy)
Status: UNCONFIRMED → NEW
Ever confirmed: true
Target Milestone: --- → mozilla1.1
confirming on Mozilla 0.9.9 (build 2002031219) on Red Hat 7.2 x86. (should this be marked as a dup of other frame problems and resolved?)
It still happens on mozilla1.0RC1 under W98SE
Keywords: crash
Talkback incident TB6926753H Captured At: 02-06-2002 18:17 OS: Windows 2000 Professional SP2, Mozilla RC3 Reproducable: yes every time When: allways (click "Terms & Conditions" as mentioned, wait, "mem exhaust") *boom* We need someone on Mac OS or another OS to confirm this. What I can confirm is this: Crasher --> critical --> happening in latest trunk/etc. builds As I said this is looking like cross platform crashing, but there weren't any Mac OS users around to confirm. If this is happening on Linux is this happening on FreeBSD? (Guessing is fun)
Adding some people ...
here is the page: http://www.english-heritage.org.uk/default.asp?wci=mainframe&URL1=default.asp%3FWCI%3DNode%26WCE%3D191 this was found on the page: <iframe id=BodyFrame name="BodyFrame" src="#" width="100%" height="100%" scrolling="yes" frameborder="0" marginwidth="0" marginheight="0"></iframe> note the src="#" I think that might be causing moz to load the current page in the frame and cause an infinite recursive chain of frames. It doesn't look as "evil" as bug 89300 though ;-)
*** Bug 127079 has been marked as a duplicate of this bug. ***
I'm confirming this on. Mozilla 1.0 Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:1.0.0) Gecko/20020530 This as you see is Mozilla 1 and after doing step three from the first posting i too had a resource problem after about 10 minutes and had to close the page before a system failure. Using Windows ME, and of course ram has nothing to do with resource drain under windows but for the record, 512 megs of DDR for a 1,4 GHz AMD
Depends on: 136580
Same behaviour on OS X 10.1.5 with a Chimera build that uses the Mozilla 1.0 libraries. Looks like a recursive frame loading issue. The loading never stops.
platform/os -> all per last two comments
OS: Linux → All
Hardware: PC → All
Priority: -- → P2
The reason caused recursive loop is <iframe ..src="#">, see bug98158 #c21. The last patch can fix this bug. duplicated of bug98158
Depends on: 98158
No longer depends on: 136580
*** Bug 160543 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of 98158 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
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.