New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 672884 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 634547
Owner:
Last visit > 30 days ago
Closed: Dec 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: Android , Windows
Pri: 2
Type: Bug



Sign in to add a comment

32-bit support for large memory allocation

Project Member Reported by mtrofin@chromium.org, Dec 9 2016

Issue description

Wasm scenarios require for their heap (==an array buffer) a large (512MB or more) linear address space.

The following page fails on Android 32 bit, on a Nexus 5, at the allocation line (where "v" is assigned)

<body>
        <script>
        var size = Math.pow(2, 29);
        var v = new ArrayBuffer(size);
            var view = new Uint8Array(v);
            for (var i = 0; i < size; ++i) {
                view[i] = i;
            }
            
            console.log(view[42] == 42);
        </script>
</body>
 
Status: Started (was: Untriaged)
Mergedinto: 634547
Status: Duplicate (was: Started)

Sign in to add a comment