What do the specs say? Is there a hidden show-stopper such as a 32-bit "size" variable in the internal data structure of BigInteger? Does the OS barf if a single object exceeds some number of gigabytes in size?
It has no lower/upper bounds, so only Out of Memory can be thrown.
Interesting...Is BigInteger bounded by RAM or by virtual memory?
And does it truly have no upper bounds (e.g., the internal variable encoding the size of a BigInteger is also a BigInteger) or does it just have yuge bounds (e.g., 64 bit int).