new WebAssembly.Instance throws RangeError
Reported by
gunkm...@gmail.com,
Mar 11 2017
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.98 Safari/537.36 Steps to reproduce the problem: 1. Go to http://etg.dek.im/funge/funge.html 2. Click 'Run' What is the expected behavior? It prints out an ASCII mandelbrot set (Firefox passes) What went wrong? Uncaught (in promise) RangeError: WebAssembly.Instance(): Wasm compilation exceeds internal limits in this context for the provided arguments at bfCompile.then.m (quire.js:305) Did this work before? No Chrome version: 57.0.2987.98 Channel: stable OS Version: 10.0 Flash Version: Befunge source of Mandelbrot program by Chris Lahey, 4/11/97 Chrome is able to run other programs from https://github.com/catseye/Befunge-93/tree/master/eg
,
Mar 11 2017
Changing from WebAssembly.compile -> new WebAssembly.Instance to WebAssembly.instantiate fixes the issue Ideally there'd be agreement between browsers about how large is too large for modules to go into WebAssembly.Instance's constructor
,
Mar 11 2017
I've updated the etg.dek.im page to now work on Chrome. Changeset: https://github.com/serprex/Befunge/commit/05b2ee6250eb1f94477eeb153a43dff6eb814706
,
Mar 13 2017
,
Mar 13 2017
This is behavior that is intended to limit the amount of jank that can be introduced on the main thread in JS. It is recommended that you use the asynchronous version of the WebAssembly API, naming the WebAssembly.compile() and WebAssembly.instantiate() methods. |
|||
►
Sign in to add a comment |
|||
Comment 1 by gunkm...@gmail.com
, Mar 11 2017