New issue
Advanced search Search tips

Issue 645204 link

Starred by 1 user

Issue metadata

Status: Duplicate
Owner: ----
Closed: Sep 2016
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Chrome crashes when sending large amount of data from web worker to main thread

Reported by dshresth...@gmail.com, Sep 8 2016

Issue description

Chrome Version       : 53.0.2785.101 m (64-bit)
URLs (if applicable) : https://jsfiddle.net/21fnf1uj/5/
Other browsers tested:
  Add OK or FAIL, along with the version, after other browsers where you
have tested this issue:
     Safari: OK
    Firefox: OK
         IE: OK

What steps will reproduce the problem?
(1) Open https://jsfiddle.net/21fnf1uj/5/ and hit start. This issue is reproducible more easily in Windows than on Mac. This will start sending 10 message / sec to a web worker. The webworker responds with 100M float32Array. The response is simply discarded by the main thread.

What is the expected result?
It should continue to print "Sending 10 messages to web worker" indefinitely.

What happens instead?
You should see "Aw Snap" screen.

Please provide any additional information below. Attach a screenshot if
possible.

Chrome Canary prints a messaging saying javascript ran out of memory. When I profile the heap, javascript heap never grows above 17MB.

 
Screen Shot 2016-09-08 at 3.16.21 PM.png
164 KB View Download
Mergedinto: 645117
Status: Duplicate (was: Unconfirmed)
Marking as duplicate per request over in issue 645117

Sign in to add a comment