New issue
Advanced search Search tips

Issue 803786 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 801604
Owner: ----
Closed: Jan 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug-Regression



Sign in to add a comment

WebAssembly unable to allocate memory more than 1GB on Google Chrome Beta 64.0.3282.99

Reported by cfakhrud...@zynga.com, Jan 19 2018

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.99 Safari/537.36

Steps to reproduce the problem:
1. Open Google Chrome Beta 64.0.3282.99 -> Developer Tools -> Console
2. run "new WebAssembly.Memory({initial:16385});"
3. Get the error "VM36:1 Uncaught RangeError: WebAssembly.Memory(): could not allocate memory"

What is the expected behavior?
Able to allocate upto 2GB on Chrome 63.0.3239.132
"new WebAssembly.Memory({initial:32767});"

What went wrong?
WebAssembly unable to allocate memory more than 1GB on Google Chrome Beta 64.0.3282.99

Did this work before? Yes Chrome 63.0.3239.132

Chrome version: 64.0.3282.99  Channel: beta
OS Version: OS X 10.12.6
Flash Version: 28.0.0.142

This causes our application to crash the moment more than 1GB memory is requested with wasm out of memory errors. We do not see such errors on Firefox.
 

Comment 1 by tkent@chromium.org, Jan 19 2018

Components: -Blink Blink>JavaScript

Comment 2 by sarves...@gmail.com, Jan 19 2018

We have ramped a portion of our application to wasm, and that would break on Chrome if the above issue is not addressed on Chrome beta 64
Mergedinto: 801604
Status: Duplicate (was: Unconfirmed)

Sign in to add a comment