Closed Bug 63743 Opened 24 years ago Closed 19 years ago

nsVoidArray::InsertElementAt() is not "out of memory" safe

Categories

(Core :: XPCOM, defect)

Product:
Core
Component:
XPCOM
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WORKSFORME
Milestone:
mozilla1.1alpha

People

(Reporter: jst, Assigned: scc)

Details

Reading the code in nsVoidArray::InsertElementAt() I realized that the method
doesn't return PR_FALSE as it should if the allocation (new) fails when it
allocates the new array buffer. Looks like most places where allocations are
made in nsVoidArray have the similar problems. This should be fixed.
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla0.9
Target Milestone: mozilla0.9 → mozilla1.1
Is this still relevant, since nsVoidArray is going away (bug 92256)?
nsVoidArray is not going away.
Did this cause bug 167439?
This no longer seems to be the case.
Status: ASSIGNED → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
No specific bug / patch referenced as the fix.

-> WORKSFORME
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Status: REOPENED → RESOLVED
Closed: 19 years ago → 19 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.