Chrome (after waiting): Uncaught RangeError: Maximum BigInt size exceeded
Mozilla (right away): Uncaught RangeError: BigInt is too large to allocate
And why different errors?
And how to execute with BigInt faster? Waiting is long in Chrome, but CPU load is only about 25%. How to use 100%?
The ECMAScript specification does not specify the error message. Only the error type, here RangeError
So when should this RangeError appear?
Different behavior: Chrome gives it during execution, Firefox - before executing.
I don't think the spec says what the minimum size that all compliant engines must support.
I would expect all to be able to support at least 2**63 because there is BigInt64Array - JavaScript | MDN
There are other areas where different implementations have different memory limits, for example the maximum number of arguments that can be passed to a function is different in different engines.
Some people said (stackoverflow) that it is a matter of available RAM. But it is not so in my experience. I just checked, and the maximum size in Chrome is much-much bigger than in Firefox. I thought it is the same.
Also, interesting how to speed up JavaScript executing making it use more CPU.