Closed
Bug 664352
Opened 15 years ago
Closed 7 years ago
"Assertion failure: FrameInfoCache::FrameInfoCache(): out of memory"
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: jruderman, Unassigned)
Details
(Keywords: assertion)
The js engine has a policy of not crashing on OOM, so I think this is a bug.
./js -A 20
Assertion failure: FrameInfoCache::FrameInfoCache(): out of memory, at /var/folders/Ru/RuL9UUUZGv85umnat33ZKU+++TM/-Tmp-/abc-a55e103ba5c6-_u3hpQ/compilePath/js/src/jstracer.cpp:1480
|
Reporter | |
Comment 1•15 years ago
|
||
Same with -A 64
|
||
Comment 2•15 years ago
|
||
This is a deliberate OUT_OF_MEMORY_ABORT. In this case, it's just due to laziness -- the OOM is in a constructor so there's no return value to indicate failure. FrameInfoCache should have an init() function separate from the constructor, as is done in various other classes.
|
Assignee | |
Updated•12 years ago
|
Assignee: general → nobody
-A no longer exists and I think our OOM story has vastly improved since. A cursory search of the following also no longer exists:
Assertion failure: FrameInfoCache::FrameInfoCache()
=> WFM
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•