New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 759503 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Aug 2017
Cc:
█ hdodda@chromium.org
gsat...@chromium.org
adamk@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 2
Type: Feature



Sign in to add a comment

Detect when there is not enough memory for ArrayBuffer

Reported by ivan.kuc...@gmail.com, Aug 28 2017 
UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.101 Safari/537.36

Steps to reproduce the problem:
Run this: https://jsfiddle.net/9hL3t0tz/1/  with paging disabled.

What is the expected behavior?
I think there shold be some exception, when the RAM runs out.

What went wrong?
When RAM runs out, the website just crashes.

Did this work before? N/A 

Chrome version: 60.0.3112.101  Channel: n/a
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: Shockwave Flash 26.0 r0

Comment 1 by schenney@chromium.org, Aug 28 2017

Components: -Blink Blink>JavaScript
Labels: -Type-Bug Type-Feature

Comment 2 by hdodda@chromium.org, Aug 30 2017

Cc: hdodda@chromium.org
Labels: Needs-Triage-M62 M-62 OS-Linux OS-Mac
Status: Untriaged (was: Unconfirmed)
Marking this as untraiged as it is feature request , so that it would get addressed by repective team.

Thanks!

Comment 3 by hablich@chromium.org, Aug 31 2017

Components: -Blink>JavaScript Blink>JavaScript>Language
Status: WontFix (was: Untriaged)
I think this is WAI. adamk@ feel free to reopen.
►

Sign in to add a comment