I encountered this bug while compiling to JS real-life Lua. This minimal code triggers it:
function a() end
while true do
break
end
This gets compiled to:
G.str['a'] = (function () {
var tmp;
return [];
})
while (true) (function() {
return;
})();
Notice the immediately-invoked function expression (IIFE) inside the while loop in the generated JS code. The Lua break statement is compiled into a return call but all it does is leave the function body, not the loop. So the loop, which should exit immediately, runs forever (and locks up the browser).
The Lua function declaration function a() end at the top is required to trigger the insertion of the IIFE and thus the bug.
I encountered this bug while compiling to JS real-life Lua. This minimal code triggers it:
This gets compiled to:
Notice the immediately-invoked function expression (IIFE) inside the while loop in the generated JS code. The Lua
breakstatement is compiled into areturncall but all it does is leave the function body, not the loop. So the loop, which should exit immediately, runs forever (and locks up the browser).The Lua function declaration
function a() endat the top is required to trigger the insertion of the IIFE and thus the bug.