ReportFatalException1

[bird8693]

Enviroment

ubuntu18

poc

function AsmModule(stdlib) {
    'use asm';
    var m1 = stdlib.fround;
    function f1() {
        var x = m1(1.5);
        var y = 1;
        y = ~~~~x;
        return ~~~x;
    }   
    return f1; 
}
var global = { Math: Math };
var asmModule = AsmModule(global);
AsmModule(268435456);
print(asmModule());
print(asmModule());

callstack

[#0] 0x555555d59fac → DebugBreak()
[#1] 0x555555d59fac → ReportFatalException(context=<optimized out>, exceptionCode=<optimized out>, reasonCode=<optimized out>, scenario=<optimized out>)
[#2] 0x555555d5a3a7 → OutOfMemory_unrecoverable_error()
[#3] 0x555557ef6673 → Js::Exception::RaiseIfScriptActive(scriptContext=0x0, kind=0x0, returnAddress=0x0)
[#4] 0x555555d5a929 → Js::Throw::OutOfMemory()
[#5] 0x5555565a9a01 → Js::InterpreterStackFrame::ProcessLinkFailedAsmJsModule(this=<optimized out>)
[#6] 0x5555565a7d18 → Js::InterpreterStackFrame::ProcessAsmJsModule(this=<optimized out>)
[#7] 0x5555565685b9 → Js::InterpreterStackFrame::Process(this=<optimized out>)

[rhuanjl]

This case and several others like it are because CC aborts if an ASMModule is called with invalid params AFTER previously being called with valid params, looking at it I cannot see why this would be done except perhaps for testing purposes?

@pleath do you know why this was done? (it's from the initial commit)

[rhuanjl]

This is by design BUT I do wonder if it is a bad design choice AND it is not per-spec, per-spec when an ASM module is called in a non-conformant way it should behave like normal JS, not abort.