Ah Snap error when allocating webassembly memory
Reported by
joe.fisc...@googlemail.com,
Mar 14 2018
|
||||
Issue description
UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.162 Safari/537.36
Steps to reproduce the problem:
1. Load a simple html file in Chrome:
<html>
<body>
<div id="output"></div>
<script>
var wasmMemory = new WebAssembly.Memory({ initial:32000, minimum:2048});
document.querySelector('#output').innerHTML = "memory allocated: "+wasmMemory.buffer.byteLength;
</script>
</body>
</html>
2. Press F5 to refresh the page.
What is the expected behavior?
The memory is either succesfully allocated, or an exception is thrown and visible in the Console.
What went wrong?
The Tab crashes with Ah Snap on every second refresh of the Page. The GC doesnt collect the webassembly memory on pressing F5, so that the reloaded page cannot allocate the memory AND does not throw an exception.
Did this work before? N/A
Chrome version: 65.0.3325.162 Channel: stable
OS Version: 10.0
Flash Version:
Works on Firefox.
,
Mar 15 2018
,
Mar 15 2018
Related: history of this bug's context: issue 820795
,
Mar 20 2018
,
Mar 27 2018
|
||||
►
Sign in to add a comment |
||||
Comment 1 by woxxom@gmail.com
, Mar 14 2018