Closed Bug 722083 Opened 12 years ago Closed 3 years ago

OOM crash on HTML Markup broken site

Categories

(Core :: DOM: Core & HTML, defect, P5)

x86
Windows 7
defect

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: alice0775, Unassigned)

References

()

Details

(Keywords: crash, hang, reproducible)

Build Identifier:
http://hg.mozilla.org/mozilla-central/rev/c07595bee6cf
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0a1) Gecko/20120127 Firefox/12.0a1 ID:20120127031148

Browser crashes on HTML Markup broken site .

Reproducible: Always

Steps to Reproduce:
1. Start Firefox with clean profile
2. Open http://www.mozdev.org/projects/nav.html

Actual Results:
  Browser crashes,
  
Expected Results:
  Browser should not crash,
Browser crashes on page with infinite page length (and hence DOM Tree).
IE terminates after 62 KB.
Should Firefox terminate page loading after 64KB?
The 64-bit build hangs but doesn't crash.
Severity: normal → critical
Crash Signature: [@ EMPTY: no crashing thread identified; corrupt dump ]
Component: General → DOM
Keywords: hang, reproducible
QA Contact: general → general
Summary: Browser crashes on HTML Markup broken site . → OOM crash on HTML Markup broken site
> The 64-bit build hangs but doesn't crash.

Probably because it doesn't run out of address space?

Oh, and the page is not infinite at all.  It's only about 60MB of HTML.  ;)
Whiteboard: DUPEME
If I wait long enough, the 32-bit build crashes: bp-aac421b1-dc1c-41eb-9bca-9d6422120215.
Build identifier: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120327 Firefox/13.0a2

Crash still occurs, but only after running out of memory it seems.
Blocks: 818839
No longer blocks: 818839
(In reply to Immatix from comment #5)
> Build identifier: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0)
> Gecko/20120327 Firefox/13.0a2
> 
> Crash still occurs, but only after running out of memory it seems.

yes.
@ EMPTY: no crashing thread identified; corrupt dump
bp-6c6af667-89a6-484e-9f31-eca5f2130710
Whiteboard: DUPEME → [dupeme]
Priority: -- → P5
Component: DOM → DOM: Core & HTML
Keywords: dupeme
Whiteboard: [dupeme]

mozdev is gone

Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.