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

Issue 640712 link

Starred by 2 users
Status: WontFix
Owner:
█ kozyatinskiy@chromium.org
Last visit > 30 days ago
Closed: Aug 2016
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 3
Type: Bug



Sign in to add a comment

Chrome can't capture "out of memory exception" in window.error

Reported by zhaoyu0...@gmail.com, Aug 24 2016 
Chrome Version: 52.0.2743.116 (Official Build) m (64-bit)

Other browsers tested:
have tested this issue:
     Safari:Not test
    Firefox:Not test
         IE:OK (Can capture exception)

What steps will reproduce the problem?
Run following code in Chrome: (produce out of memory)
        window.onerror = function (msg) {
            alert(msg);
            return false;
        };

        var data = [];
        window.setInterval(function () {
            for (var i = 0; i < 100000; i++) {
                data.push({ id: i, p1: i, p2: i });
            }
        }, 1);

What is the expected result?
Capture "Out of memory" exception in window.error. I want to log and determine how many users encountered this error.

What happens instead?
Chrome will crash and shows "aw snap something went wrong while displaying this webpage". The browser can't log anything to server.

Please provide any additional information below. Attach a screenshot if
possible.
OutOfMemory.html
561 bytes View Download

Comment 1 by kavvaru@chromium.org, Aug 25 2016

Components: Platform>DevTools>Memory
Labels: M-54 OS-Linux OS-Mac OS-Windows
Status: Untriaged (was: Unconfirmed)
Able to reproduce the issue on windows 7, Linux Ubuntu 14.04 and Mac 10.11.6 using chrome version 52.0.2743.116 and canary 54.0.2838.2 with the below steps

1. Run the code in devtools console
2.Chrome tab crashed.

This is reproducible on ALL OS and it is non regression issue as the issue seen from M35 old builds.Marking it as Untriaged to get more inputs from dev team.

Thanks,

Comment 2 by zhaoyu0...@gmail.com, Aug 25 2016 

Thanks kavvaru! The crash is expected. The bug is Chrome can't capture the exception in window.error before crash. So developer are not able to log it.

Comment 3 by lushnikov@chromium.org, Aug 26 2016

Owner: kozyatinskiy@chromium.org
Status: Assigned (was: Untriaged)
I'm not sure there's something we can do here. Alexey, any thoughts?

Comment 4 by kozyatinskiy@chromium.org, Aug 27 2016

Status: WontFix (was: Assigned)
Out of memory exception isn't part of spec. We can't implement it without spec because there are a lot of tricky questions.
User needs some memory to send something to server, how we need to reserve it or we need to be able to free some memory after OOM. Or we can introduce some API like please make this fetch request when OOM happens and forbid everything else on OOM.
For now it's wontfix, JavaScript world doesn't ready for this.
►

Sign in to add a comment