Closed
Bug 529287
Opened 15 years ago
Closed 15 years ago
OOM during GC constructor could cause crash during Collect of uninitialized values
Categories
(Tamarin Graveyard :: Virtual Machine, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: bgetlin, Assigned: lhansen)
Details
Attachments
(1 file)
|
480 bytes,
patch
|
lhansen
:
review+
|
Details | Diff | Splinter Review |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US) AppleWebKit/532.0 (KHTML, like Gecko) Chrome/3.0.195.33 Safari/532.0
Build Identifier:
Move GC memory initialization routines before adding the OOMcallback and GC to the heap list. This ensures the GC will be fully initialized in case OOM is invoked during the constructor.
Reproducible: Sometimes
|
Reporter | |
Comment 1•15 years ago
|
||
Perforce checkin : 603576
Attachment #412858 -
Flags: review?(lhansen)
|
Assignee | |
Updated•15 years ago
|
Attachment #412858 -
Flags: review?(lhansen) → review+
|
|
Assignee | |
Comment 2•15 years ago
|
||
I will land.
Assignee: nobody → lhansen
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
|
|
Assignee | |
Comment 3•15 years ago
|
||
redux changeset: 3177:db13d79c2052
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•