Closed Bug 306812 Opened 19 years ago Closed 9 years ago

should cryptojs_ReadArgsAndGenerateKey handle oom better

Categories

(Core :: Security: PSM, defect, P5)

Product:
Core
Component:
Security: PSM
Platform:
x86
Windows XP
Type:
defect

Tracking

()

Status:
RESOLVED INVALID

People

(Reporter: timeless, Unassigned)

References

(
URL
)

Details

(Whiteboard: [kerh-cuz]) 

if JS_ValueToString fails because of oom, the errors reported by this code will
be fairly bogus.
this code path will assert for one oom if it doesn't crash right away from the
other :)
http://bonsai.mozilla.org/cvsblame.cgi?file=mozilla/security/manager/ssl/src/nsCrypto.cpp&rev=1.55&mark=1468-1469,1576-1577,1364-1365,1383,1176,1215,922,925#1415

JS_ValueToString can fail.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Priority: -- → P5
Whiteboard: [kerh-cuz]
QA Contact: psm
reassign bug owner.
mass-update-kaie-20120918
Assignee: kaie → nobody
The relevant code doesn't appear to exist anymore.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.