Closed Bug 991694 Opened 10 years ago Closed 10 years ago

Assertion failure: [unhandlable oom] Failed to allocate object while tenuring., at c:\work\mozilla\builds\nightly\mozilla\js\src\jscntxt.cpp:1373

Categories

(Core :: JavaScript Engine, defect)

x86
Windows 7
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 999158

People

(Reporter: cbook, Unassigned)

References

()

Details

Attachments

(1 file)

Attached file windows crash report
found via bughunter on http://www.cahba.com/advice/covered_california/

Loading this site result in a win7 trunk debug build based on latest m-c tip after awhile during load in

Assertion failure: [unhandlable oom] Failed to allocate object while tenuring., at c:\work\mozilla\builds\nightly\mozilla\js\src\jscntxt.cpp:1373
Hit MOZ_CRASH() at c:\work\mozilla\builds\nightly\mozilla\js\src\jscntxt.cpp:1374
[324] ###!!! ABORT: Aborting on channel error.: file c:\work\mozilla\builds\nightly\mozilla\ipc\glue\MessageChannel.cpp, line 1522

will see that i can get a testcase/regression range
Blocks: 994589
Group: core-security
Why is this sec-private?
Flags: needinfo?(mwobensmith)
(In reply to Benjamin Smedberg  [:bsmedberg] from comment #1)
> Why is this sec-private?

I was asked to make it private by Liz Henry, who is doing some work on security-related bugs.
Flags: needinfo?(mwobensmith)
Why is this sec-private?
Flags: needinfo?(lhenry)
Terrence, I wasn't sure if it should be or not; I'm going through all the GGC bugs for Nightly and noticed this comment: https://bugzilla.mozilla.org/show_bug.cgi?id=992866#c1   I thought this might be similar. If it isn't, sorry about that!
Flags: needinfo?(lhenry)
Also, I just realized this isn't tagged GGC but I think it was filed as a result of one of the GGC bugs. Probably my mistake.
Ah, gotcha! CrashAtUnhandlableOOM is a straight-up crash, even in opt builds, so cannot be exploited. It prints "Assertion failure" only because we re-used the assertion printing machinery to ensure the print gets in the right dumps. Sorry for the confusion!
Group: core-security
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: