Re: [whatwg] Handling out of memory issues with getImageData/createImageData

2015-09-28 Thread Justin Novosad
On Mon, Sep 28, 2015 at 5:40 AM, Anne van Kesteren wrote: > On Sun, Sep 27, 2015 at 6:14 PM, Allen Wirfs-Brock > wrote: > > Actually, that's not completely correct. Within ES2015, the only way > > explicitly allocate a large, dense area of memory is by

Re: [whatwg] Handling out of memory issues with getImageData/createImageData

2015-09-28 Thread Anne van Kesteren
On Sun, Sep 27, 2015 at 6:14 PM, Allen Wirfs-Brock wrote: > Actually, that's not completely correct. Within ES2015, the only way > explicitly allocate a large, dense area of memory is by creating a large > ArrayBuffer instance. All attempts to create such instances

Re: [whatwg] Handling out of memory issues with getImageData/createImageData

2015-09-27 Thread Mark S. Miller
On Sat, Sep 26, 2015 at 7:34 AM, Anne van Kesteren wrote: > On Fri, Sep 25, 2015 at 4:48 PM, Justin Novosad 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

Re: [whatwg] Handling out of memory issues with getImageData/createImageData

2015-09-27 Thread Mark S. Miller
van Kesteren > Sent: zaterdag 26 september 2015 16:35 > To: Justin Novosad <ju...@google.com> > Cc: WHAT Working Group <wha...@whatwg.org>; Mark Miller <erig...@gmail.com > > > Subject: Re: [whatwg] Handling out of memory issues with > getImageData/createImageDa

Re: [whatwg] Handling out of memory issues with getImageData/createImageData

2015-09-27 Thread Mark S. Miller
Since my post is about the more general OOM issue, I have shifted the discussion to es-discuss https://mail.mozilla.org/pipermail/es-discuss/2015-September/044267.html Please continue discussion of the non-browser-specific issue there. On Sun, Sep 27, 2015 at 8:33 AM, Mark S. Miller

Re: [whatwg] Handling out of memory issues with getImageData/createImageData

2015-09-27 Thread Allen Wirfs-Brock
On Sep 26, 2015, at 7:34 AM, Anne van Kesteren wrote: > On Fri, Sep 25, 2015 at 4:48 PM, Justin Novosad 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

Re: [whatwg] Handling out of memory issues with getImageData/createImageData

2015-09-27 Thread Mark S. Miller
I should make it clear that my post is not concerned about OOM for image data -- the original subject of this thread -- but rather about the more general OOM question that Anne asks about. On Sat, Sep 26, 2015 at 9:15 PM, Rik Cabanier wrote: > On Fri, Sep 25, 2015 at 7:51

Re: [whatwg] Handling out of memory issues with getImageData/createImageData

2015-09-27 Thread Mark S. Miller
On Sun, Sep 27, 2015 at 8:30 AM, Mark S. Miller wrote: > On Sat, Sep 26, 2015 at 7:34 AM, Anne van Kesteren > wrote: > >> On Fri, Sep 25, 2015 at 4:48 PM, Justin Novosad wrote: >> > Currently there is no spec'ed behavior for handling

Re: [whatwg] Handling out of memory issues with getImageData/createImageData

2015-09-26 Thread Niels Keurentjes
dag 26 september 2015 16:35 To: Justin Novosad <ju...@google.com> Cc: WHAT Working Group <wha...@whatwg.org>; Mark Miller <erig...@gmail.com> Subject: Re: [whatwg] Handling out of memory issues with getImageData/createImageData On Fri, Sep 25, 2015 at 4:48 PM, Justin Novosad

Re: [whatwg] Handling out of memory issues with getImageData/createImageData

2015-09-26 Thread Rik Cabanier
On Fri, Sep 25, 2015 at 7:51 AM, Boris Zbarsky wrote: > On 9/25/15 10:48 AM, Justin Novosad wrote: > >> I am sharing this here in case there would be interest in standardizing >> this behavior. >> > > I personally think it's a good idea (and throwing an exception is how > Gecko

Re: [whatwg] Handling out of memory issues with getImageData/createImageData

2015-09-26 Thread Anne van Kesteren
On Fri, Sep 25, 2015 at 4:48 PM, Justin Novosad 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

Re: [whatwg] Handling out of memory issues with getImageData/createImageData

2015-09-25 Thread Boris Zbarsky
On 9/25/15 10:48 AM, Justin Novosad wrote: I am sharing this here in case there would be interest in standardizing this behavior. I personally think it's a good idea (and throwing an exception is how Gecko handles, or at least aims to handle, this situation). -Boris