The "Aw snap page" appears when filtering big arrays
Reported by
remi.ven...@gmail.com,
Oct 18 2016
|
|||||||||||
Issue description
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:49.0) Gecko/20100101 Firefox/49.0
Steps to reproduce the problem:
var a = [];
for(var i = 0; i < 90000000; i++){
a.push(Math.floor(Math.random() * 10) + 1);
}
var b = a.filter(v => v <= 5); //Crash here
What is the expected behavior?
b is an array filled with the values from a which are less or equal to 5.
What went wrong?
The "Aw, Snap!" page appears suddenly.
On my machine, I can successfully filter an array with a maximum length of 69761755 values. If I add one or more value(s), the bug appears every time.
I checked applying others array functions, such as map or reduce, they both work well.
Did this work before? N/A
Chrome version: 53.0.2785.143 (64-bit) Channel: stable
OS Version: OS X 10.12
Flash Version: Shockwave Flash 23.0 r0
,
Oct 19 2016
,
Oct 19 2016
Able to reproduce this issue on Mac 10.12,Windows 10 and Ubuntu 14.04 on latest chrome Stable version 54.0.2840.59. Issue is broken in M49. Below are the bisect details for the same: Bisect Info: =========== Good Build : 49.0.2616.0, Revision Range (368227) Bad Build : 49.0.2617.0 , Revision Range (368501) After executing the bisecting script, got the following the ChangeLog URL: https://chromium.googlesource.com/chromium/src/+log/7fe28ea1c28121d7a595353a5b2a571686721a97..52d99ec2012ebee7aef33583feb6a082cacb479b The suspecting Change Log is : ----------- https://chromium.googlesource.com/chromium/src/+/bd9c806a5784da8805fd2b90eec8d15ad1057b3f From the above CL suspecting the below change Review URL: https://codereview.chromium.org/1569983004 senorblanco@- Could you please look into this issue, if it's related to your change? if not could you please help us to reassign this issue to the right owner. Thanks.!
,
Oct 19 2016
,
Oct 19 2016
The "filter" in the above CL refers to CSS image filters, and is unrelated to the javascript filter() function.
,
Nov 25 2016
Still we are bale to reproduce the same issue on Windows 7 with Chrome stable version#54.0.2840.99 & Latest canary #57.0.2931.0. As per Comment#5,Unable to find the suspect from the above CL .Could anybody from dev team please help us on the same. Thank you.
,
Nov 27 2017
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 28 2017
,
Nov 28
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Dec 4
Sounds like an OOM an working as intended?
,
Dec 4
This does not repro anymore, it looks like we raised the limit at some point. |
|||||||||||
►
Sign in to add a comment |
|||||||||||
Comment 1 by remi.ven...@gmail.com
, Oct 18 2016