Closed Bug 41727 Opened 24 years ago Closed 24 years ago

Out of memory issue with JS Exception objects

Categories

(Core :: JavaScript Engine, defect, P3)

defect

Tracking

()

VERIFIED DUPLICATE of bug 46196

People

(Reporter: pschwartau, Assigned: mike+mozilla)

Details

(Keywords: js1.5)

Errors as exceptions should not try to create a new Exception object when you're 
out of memory
Keywords: js1.5
Summary: Out of memory issue with Exception objects → Out of memory issue with JS Exception objects
Taking bugs off Roger's plate.
Assignee: rogerl → mccabe
Status: NEW → ASSIGNED
Potential crasher; nominating nsbeta3.
Keywords: nsbeta3
How potential? Have we seen crashing instances of this? I agree, if a simple fix 
is possible, we should attempt it.
How about changing JS_ReportOutOfMemory to send the 'out of memory' directly to 
the context's error reporter without calling any of the rest of the error 
infrastructure?  At the same time, change the error handling code throughout to 
call JS_ReportOutOfMemory whenever an allocation fails and avoid any chance of 
recursion or crashing. 
I'm marking this as a dup of 46196, rather than the other way around since 46196 
has some other interesting comments about places we miss error testing for 
allocation failures. Anybody that'd like to comment on a good solution is 
welcome to do so...

*** This bug has been marked as a duplicate of 46196 ***
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
Verifying duplicate -
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.