Closed
Bug 746264
Opened 13 years ago
Closed 7 years ago
[jsdbg2] Debugger should not try to catch stack overflow and OOM conditions
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
RESOLVED
INACTIVE
People
(Reporter: jimb, Unassigned)
Details
At the moment, if the stack overflows or the program runs out of memory while we're running a Debugger event handler method, Debugger still tries to pass that to uncaughtExceptionHandler, which can't do much but flail around getting more stack overflows and OOMs of its own.
Stack overflow and out-of-memory are sort of uncatchable conditions; the debugger should probably not try to treat them like other kinds of abrupt termination.
|
Reporter | |
Comment 1•13 years ago
|
||
Jason Orendorff points out that stack overflow is a catchable exception. I think the intent here is more that they *should* not be caught, because they can't be handled effectively.
|
Assignee | |
Updated•11 years ago
|
Assignee: general → nobody
Jim, our OOM story seems to have changed much since ~7 years ago, would things have changed wrt. comment 0?
Flags: needinfo?(jimb)
|
|
Reporter | |
Comment 3•7 years ago
|
||
Resolving this isn't a priority, either way.
Status: NEW → RESOLVED
Closed: 7 years ago
Flags: needinfo?(jimb)
Resolution: --- → INACTIVE
You need to log in
before you can comment on or make changes to this bug.
Description
•