New issue
Advanced search Search tips

Issue 593272 link

Starred by 2 users
Status: Assigned
Owner:
kinuko@chromium.org
Cc:
ajha@chromium.org
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 2
Type: Bug-Regression



Sign in to add a comment

processor intensive scripts often incorrectly trigger 'aw snap' instead of the unresponsive page invitation

Reported by john.atw...@gmail.com, Mar 9 2016 
UserAgent: Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.75 Safari/537.36

Steps to reproduce the problem:
1. Run any working processor-intensive script
2. Occasionally instead of the prompt to wait for it to finish, the browser gives the 'aw snap' message and the script is incorrectly terminated

What is the expected behavior?
The unresponsive page warning should appear including the 'wait' prompt to give the user the option of letting the script finish

Note: the debug log is from when this script was embedded in a larger page, but I am sure that the crash was because this script did not finish in time.

What went wrong?
Chrome crashed

Crashed report ID: sorry ('crash reporting is disabled')

How much crashed? Just one tab

Is it a problem with a plugin? N/A 

Did this work before? Yes Always

Chrome version: 49.0.2623.75  Channel: beta
OS Version: 6.3
Flash Version: Shockwave Flash 20.0 r0

Hi, I've attached a script and also a chrome_debug.log. The log file is from when this one function was being called in a larger page, I have extracted the offending script so you can see it. The problem is *intermittent* but affects all computers, so I hope it is helpful to see the errors which it generated during this crash.
partitions.html
964 bytes View Download
chrome_debug.log
53.1 KB View Download

Comment 1 by john.atw...@gmail.com, Mar 9 2016 

OK here is a better pair of files. I cleaned up the extraneous html tags at the end of the file partitions.html just to be sure that was not a cause, and this chrome debug log is from this actual file (complicated because other tabs were open).

This time, there *were* unresponsive page warnings, but when I clicked to continue the script it then crashed with 'aw snap' anyway.
partitions.html
936 bytes View Download
chrome_debug (2).log
52.5 KB View Download

Comment 2 by john.atw...@gmail.com, Mar 9 2016 

OK I ran it with crash reporting enabled, and here is the crash report number

Crash ID 6394a73400000000 (9580b757-58f8-4455-8d29-c95c9829b898)

Also, *crucially* the reason I'm reporting this is because it affects web workers, where it is really hard to trace and diagnose.

Comment 3 by brajkumar@chromium.org, Mar 10 2016 

 Issue 593444  has been merged into this issue.

Comment 4 by ajha@chromium.org, Mar 10 2016

Cc: ajha@chromium.org
Labels: -OS-Windows -Type-Bug M-51 hasbisect OS-All Type-Bug-Regression
Owner: kinuko@chromium.org
Status: Assigned (was: Unconfirmed)
Able to reproduce this on the latest stable(49.0.2623.87) and the latest canary(51.0.2673.0) on Windows-7, Mac OS 10.11.3 and Linux Ubuntu 14.04.

This is a regression issue broken in M-35.

Last good build: 35.0.1911.0
First bad build: 35.0.1912.0

Changelog:
============
https://chromium.googlesource.com/chromium/src/+log/629ec27203654b8b8e02bd5b03814a4ce86cb97c..6b18e04de9b05cb956a69f2537f0bceb92109493

Suspecting: https://codereview.chromium.org/206783004

Looks like  rvargas@ is doing something else hence assigning to kinuko@(one of the reviewers) for help in investigating this further. Feel free to re-assign if the change is not related.

Thank you!

Comment 5 by john.atw...@gmail.com, Mar 10 2016 

Just to say, a comment on the corresponding  issue 593444  correctly said it looks like an oom issue. 

When I run my program while watching the windows task manager memory manager, I can see the memory filling up. 

This is not a chrome bug ... should I withdraw the bug report somehow? 

It would be nice if there were some sort of error in chrome_debug.log to help developers, but there is no bug in chrome.

John
►

Sign in to add a comment