No no no. You don’t realise the compiled intermediate can be _trivially_ reused for every request, and identified by the hash of the JavaScript code. Browsers already do this, it’s just your attacker has a bigger cache, and not by a little bit.
Browsers _intentionally_ limit the amount of memory and cpu cycles a tab can consume to make for a nicer human experience.
Browsers _intentionally_ limit the amount of memory and cpu cycles a tab can consume to make for a nicer human experience.