Issue metadata
Sign in to add a comment
|
Scripts like this one cause Chrome to crash
Reported by
john.atw...@gmail.com,
Mar 9 2016
|
||||||||||||||||||||
Issue descriptionUserAgent: 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. Browse to the attached file "partitions.html". Press the button labelled "press this to cause crash". to start the sample script. 2. Press "wait" if necessary to prevent time-out (this is to show how this and many other scripts fail on all computers when used as a web-worker). 3. The browser crashes. The chrome_debug.log file appears to have no errors. What is the expected behavior? The browser should not crash. What went wrong? The browser crashes on this or any other script or web-worker which is processor-intensive. Crashed report ID: Crash ID 212bf02800000000 (8986909c-fa7e-473d-9726-bf10400298eb) How much crashed? Just one tab Is it a problem with a plugin? No Did this work before? Yes Chrome version: 49.0.2623.75 Channel: beta OS Version: 6.3 Flash Version: Shockwave Flash 20.0 r0 NOTE: I reported this in report number 593272 but explained things in a lengthy way. Here I have also disabled extensions, incuded the crash report and chrome-debug.log etc. It is worrying that chrome_debug.log has no errors.
,
Mar 9 2016
Thanks for reporting! This is a duplicate of issue 593272, I'm able to repro this crash in beta (49.0.2623.87) on windows. Crash ID a9ecbf3400000000 (c1c7b114-9432-4725-89c2-ba3e62c03614).
,
Mar 9 2016
Both crash reports referenced in the original issue are OOM crashers.
,
Mar 10 2016
As per comment 2 confirming the issue looks similar to bug 593272, Hence merging in to it.
,
Mar 10 2016
Hi, (I'm the original commenter): It is totally possible that the script is demanding more array space than is available. It is building about a 20 megabyte array, but since it is a recursive function call (with 2 arguments) there are many such 20 megabyte arrays which are subsidiary local variables. Maybe there is nothing wrong, except it would be nice if developer's console or chrome_debug or the aw_snap message mentioned that it is out of memory for sake of developeres. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by john.atw...@gmail.com
, Mar 9 2016