On 9/26/13 4:35 PM, Benjamin Peterson wrote:
How much is this a JS problem compared to a Gecko one? IIRC, almost
everywhere outside of JS just crashes if it can't allocate memory.
It depends.
Almost everywhere outside JS crashes on failure of _small_ allocations.
Large allocations (esp ones w
How much is this a JS problem compared to a Gecko one? IIRC, almost
everywhere outside of JS just crashes if it can't allocate memory.
2013/9/26 Gregor Wagner :
> I don't know if the roadmap is the right place for this but I would also love
> to see
> some effort dealing with OOM situations. In t
On 9/26/13 4:27 PM, Gregor Wagner wrote:
I don't know what the right approach is. Maybe a testing framework or static
analysis for
proper OOM error propagation but we will see these kinds of problems more often
once people start
writing apps with higher memory requirements for b2g.
Will those
On Thu, Sep 26, 2013 at 1:27 PM, Gregor Wagner wrote:
> I don't know if the roadmap is the right place for this but I would also love
> to see
> some effort dealing with OOM situations.
>
> I don't know what the right approach is. Maybe a testing framework or static
> analysis for
> proper OOM e
I don't know if the roadmap is the right place for this but I would also love
to see
some effort dealing with OOM situations. In the desktop world we practically
never hit this case
but for b2g we have to rely on proper OOM handling.
We already fixed a few bugs where we allocate too much memory d
On 09/24/2013 06:20 PM, Chris Peterson wrote:
> After collecting a list of the active SpiderMonkey projects [1], Naveed
> asked me to present the projects on a roadmap for the next four
> quarters. Here is a rough draft:
>
> https://wiki.mozilla.org/User:Cpeterson/Roadmap#Roadmap
>
> * Are any im
6 matches
Mail list logo
