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

Issue metadata

Status: Duplicate
Merged: issue v8:7740
Closed: May 2018
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug-Regression

Sign in to add a comment

Issue 839848: Crash on page with lots of Canvas updates

Reported by, May 4 2018

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.139 Safari/537.36

Steps to reproduce the problem:
1. Browse to
2. Wait a few seconds to a few minutes
3. Aw, Snap!

What is the expected behavior?
The page should update every 5 seconds or so for 20 minutes before timing out.

What went wrong?
Crashes with Aw, Snap! error.

Crashed report ID: a949d5123a1fe70e 

How much crashed? Just one tab

Is it a problem with a plugin? No 

Did this work before? Yes 65

Chrome version: 66.0.3359.139  Channel: stable
OS Version: 10.0
Flash Version: 

This page (and many others using the same gauges code) has worked fine for years in previous versions of Chrome. It continues to work correctly in other browsers (tested IE 11, Edge, Firefox, and Safari)

Comment 1 by, May 4 2018

Components: Blink>JavaScript

Comment 2 Deleted

Comment 3 by, May 4 2018

I can confirm this issue, AND it also crashes other tabbed windows in Chrome 66 at the same time with either "Aw, Snap!" or "Cant open this page" errors

Comment 4 by, May 4 2018

Yep same here as mentioned above. Worked for years till 66. All other browsers no issue. Just Chrome.

Comment 5 by, May 5 2018

Me To

You can see it at

Comment 6 by, May 6 2018

Same here. Exactly as above.

Comment 7 by, May 6 2018

Wild stab... is this something to do with SetTimeout() and the stack?
Each call to setTimeout() is now being pushed onto the stack, I do not see this with Firefox, the stack there only contains the last async call to update() in the code below. Chrome 66 the stack just grows continuously.

<html lang="en">
        var count = 0;
        function update() {
            document.getElementById('update_me').innerHTML = count;
            setTimeout(update, 1);
        setTimeout(update, 1);
    <div id="update_me"></div>

Comment 8 by, May 6 2018

I am also confirming this.

Comment 9 by, May 7 2018

Mergedinto: 838503
Status: Duplicate (was: Unconfirmed)
Thanks for filing the issue. As per the provided crash id in C#0, seems this issue is similar to #838503 hence merging into it.

Feel free to undup if it is not similar.

Comment 10 by, May 8 2018

I do not think this is a duplicate of 838503, the crash happens when the dev tools are not running.

Comment 11 by, May 9 2018

I am also getting this issue on Cumulus MX (http://localhost:8998/index.html). I am running Chrome on a Mac High Sierra 10.13.4 (17E202).  The Cumulus MX page reloads fine every time manually but then 2-3 minutes later it goes Aw Snap again.

Comment 12 by, May 14 2018

Status: Untriaged (was: Duplicate)
838503 is specific to DevTools. Unmerging.

Comment 13 by, May 15 2018

I can't reproduce it on my Mac. Yang, Jakob, Andreas any clue?

Comment 14 by, May 15 2018

Comment 15 by, May 15 2018

Labels: -Pri-2 Pri-1
Status: Assigned (was: Untriaged)
Thanks Ulan and Georg. Can you please set this bug to fixed when appropriate and request a merge to 67 after some Canary coverage?

Comment 16 by, May 15 2018


Comment 17 by, May 15 2018

Mergedinto: -838503 v8:7740
Status: Duplicate (was: Assigned)

Sign in to add a comment