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 creating a large
> > ArrayBuffer instance.
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 eventually
> perform the actio
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 APIs.
>
> Actually,
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 wrote:
> I
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 out-of memory issues
>> > for the specific case of attempting
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 AM, Boris Zbarsky wro
Of Anne
> van Kesteren
> Sent: zaterdag 26 september 2015 16:35
> To: Justin Novosad
> Cc: WHAT Working Group ; Mark Miller >
> Subject: Re: [whatwg] Handling out of memory issues with
> getImageData/createImageData
>
> On Fri, Sep 25, 2015 at 4:48 PM, Justin Novosad 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 out-of memory issues
> > for the specific case of attempting to allocate a large buffer through
> > image data APIs.
>
> Actu
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 handles, or at lea
ren
Sent: zaterdag 26 september 2015 16:35
To: Justin Novosad
Cc: WHAT Working Group ; Mark Miller
Subject: Re: [whatwg] Handling out of memory issues with
getImageData/createImageData
On Fri, Sep 25, 2015 at 4:48 PM, Justin Novosad wrote:
> Currently there is no spec'ed behavior for
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 out-of-memory behavior,
period
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
Hi All,
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.
In Chrome, the current behavior is to crash the process (out of memory
exception), which results in a "sad browser tab". We are
13 matches
Mail list logo
