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 <[email protected]>: > 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 during parsing > or type analysis but finding and debugging these kind of errors always needs > multiple people spending > multiple days with the problem. > Like bug 884394 for example where multiple people already spent days > debugging the problem and it > looks like that we don't handle an OOM situation somewhere within the JS > engine gracefully. But we are still not sure. > > 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. > > -Gregor > > On Sep 26, 2013, at 12:44 PM, Steve Fink <[email protected]> wrote: > >> 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 important projects or categories missing? >> >> There's "Memory-dependent GC Configuration", but do we want to do >> anything specifically to address the memory problems that are resulting >> in b2g needing to implement things in C++ rather than JS? It just seems >> like it ought to be the other way around. >> >> Not that I've really thought about how to fix it. Nursery-only run mode >> + swapping more stuff to persistent storage? (Is this what the startup >> cache is for?) >> >> _______________________________________________ >> dev-tech-js-engine-internals mailing list >> [email protected] >> https://lists.mozilla.org/listinfo/dev-tech-js-engine-internals > > _______________________________________________ > dev-tech-js-engine-internals mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-tech-js-engine-internals -- Regards, Benjamin _______________________________________________ dev-tech-js-engine-internals mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-js-engine-internals
