- From: Anne van Kesteren <annevk@annevk.nl>
- Date: Sat, 26 Sep 2015 16:34:36 +0200
- To: Justin Novosad <junov@google.com>
- Cc: WHAT Working Group <whatwg@whatwg.org>, Mark Miller <erights@gmail.com>
On Fri, Sep 25, 2015 at 4:48 PM, Justin Novosad <junov@google.com> wrote: > Currently there is no spec'ed behavior for handling out-of memory issues > for the specific case of attempting to allocate a large buffer through > image data APIs. Actually, there is no specified behavior for out-of-memory behavior, period. This is a problem that starts with the ECMAScript standard and everything that builds upon it. I have seen Mark Miller discuss some of the issues surrounding this and perhaps even the necessity to eventually define it, but so far this has not happened. Not sure if the full story is documented somewhere. Mark? https://esdiscuss.org/topic/using-max-stack-limit-to-determine-current-js-engine-and-revision#content-7 indicates there may be security issues with throwing out-of-memory exceptions. -- https://annevankesteren.nl/
Received on Saturday, 26 September 2015 14:35:07 UTC