Bug 969757 - Remove support for OS/2
Bug 969865 - Fix the allocation handling of frame time recording

FramesTimingRecording::mIntervals should use fallible allocations, as
the code which is using it is prepared to handle OOM conditions.
However, this handling is not required for the array argument passed to
LayerManager::StopFrameTimeRecording, since that array is coming from
the IPDL protocol, and as of bug 967167 we handle the OOM conditions at
the IPDL protocol layer properly, so no extra OOM handling is necessary
here.

https://bugzilla.mozilla.org/show_bug.cgi?id=969865
Use fallible allocations in some places in our plugin code

It seems like the sizes for these data structures can be controlled from
Web content, and we are already prepared to deal with OOM conditions,
except that we are using infallible allocations by mistake.
Use fallible allocation in WebGL element array cache; r=bjacob

It seems like the sizes for these data structures can be controlled from
Web content, and we are already prepared to deal with OOM conditions,
except that we are using infallible allocations by mistake.
Use fallible allocations to store the used attributes of a WebGL program

It seems like the sizes for these data structures can be controlled from
Web content, and we are already prepared to deal with OOM conditions,
except that we are using infallible allocations by mistake.
Do not try to check the return value of nsTArray::SetLength in nsLocaleService

This size is not controllable from content. and nsTArray::SetLength's
return value is always true for now (I'm converting it to void in bug
969864.)
Use fallible allocations in the URL Classifier some more
Use fallible allocation in the icon decoder for Mac

It seems like the sizes for these data structures can be controlled from
Web content, and we are already prepared to deal with OOM conditions,
except that we are using infallible allocations by mistake.
Do not try to check the return value of nsTArray::SetLength in nsDateTimeFormatMac::FormatTMTime

This size is not controllable from content. and nsTArray::SetLength's
return value is always true for now (I'm converting it to void in bug
969864.)
Use fallible allocation to store the style information for CSS transitions and animations

It seems like the sizes for these data structures can be controlled from
Web content, and we are already prepared to deal with OOM conditions,
except that we are using infallible allocations by mistake.
Use fallible allocations for storing the right and bottom border information for table cells

It seems like the sizes for these data structures can be controlled from
Web content, and we are already prepared to deal with OOM conditions,
except that we are using infallible allocations by mistake.
Bug 969864 - Make nsTArray::SetLength return void; r=froydnj