Closed
Bug 856794
Opened 12 years ago
Closed 12 years ago
fix callers of infallible nsTArray::EnsureLengthAtleast() to not look at the return type, in SetBackgroundList / SetBackgroundPairList
Categories
(Core :: CSS Parsing and Computation, defect)
Core
CSS Parsing and Computation
Tracking
()
RESOLVED
FIXED
mozilla23
People
(Reporter: tbsaunde, Assigned: tbsaunde)
References
Details
Attachments
(1 file)
3.32 KB,
patch
|
heycam
:
review+
|
Details | Diff | Splinter Review |
No description provided.
Assignee | ||
Comment 1•12 years ago
|
||
Attachment #732040 -
Flags: review?(dholbert)
Comment 2•12 years ago
|
||
Comment on attachment 732040 [details] [diff] [review]
bug 856794 - don't check the return value of nsTArray::EnsureLengthAtleast()
Looks like this code was added in bug 322475 and bug 576044 by zwol.
Probably worth getting his input on this. If this code is a way for web developers to easily make us allocate an arbitrarily large amount of memory[1], then we may want to switch to a fallible array and keep the alloc-failed fallback code.
--> kicking review over to zwol.
[1] (I'm not sure offhand if this is the case or not, for this code. But that's my rough internal heuristic for "should we be using fallible memory-allocation?")
Attachment #732040 -
Flags: review?(dholbert) → review?(zackw)
Updated•12 years ago
|
Summary: fix callers of infalible nsTArray::EnsureLengthAtleast() to not look at the return type → fix callers of infallible nsTArray::EnsureLengthAtleast() to not look at the return type, in SetBackgroundList / SetBackgroundPairList
Version: unspecified → Trunk
Comment 3•12 years ago
|
||
Comment on attachment 732040 [details] [diff] [review]
bug 856794 - don't check the return value of nsTArray::EnsureLengthAtleast()
In general, CSS can only make the parser / rule processor allocate memory linear in the size of the style sheet, and on that basis we haven't really even tried to make it robust against out-of-memory, despite appearances. I wrote a patch at one point to rely on infallible malloc from the parser proper; don't remember if it ever landed.
So I think this is safe, but I'm going to forward review to Cameron, because I haven't looked at nsRuleNode in quite some time and I might not know something important.
Attachment #732040 -
Flags: review?(zackw) → review?(cam)
Comment 4•12 years ago
|
||
Comment on attachment 732040 [details] [diff] [review]
bug 856794 - don't check the return value of nsTArray::EnsureLengthAtleast()
Yeah this seems safe to me.
Attachment #732040 -
Flags: review?(cam) → review+
Assignee | ||
Comment 5•12 years ago
|
||
Comment 6•12 years ago
|
||
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla23
You need to log in
before you can comment on or make changes to this bug.
Description
•