Uncaught RangeError: Maximum call stack in JavaScript

1) Non-Terminating Recursive functions

Browser allocates memory to all data types. Sometimes calling a recursive function over and over again, causes the browser to send you this message as the memory that can be allocated for your use in not unlimited.

There is nothing painful for a coder than a non-terminating function or a method of recursion that tends to get stuck in an infinite loop.

Be considerate while calling functions, also dry run is the best practice to prevent them.

Maximum call stack gets overflow and washes away your hopes of running the code correctly.(XD)

Chasing down a runaway recursive call uses the same memory-profiling techniques covered in debugging memory leaks in JavaScript.

var a = new Array(4294967295);  //OK
var b = new Array(-1); //range error

var num = 2.555555;
document.writeln(num.toExponential(4));  //OK
document.writeln(num.toExponential(-2)); //range error!

num = 2.9999;
document.writeln(num.toFixed(2));   //OK
document.writeln(num.toFixed(25));  //range error!

num = 2.3456;
document.writeln(num.toPrecision(1));   //OK
document.writeln(num.toPrecision(22));  //range error!

2) Out of Range

If someone asks you what your name is.

You won’t reply ‘2000 yrs’.

var num = 1;
try {
     num.toPrecision(500);  //no can't have 500 significant digits
    }
catch(err) {
     document.getElementById("mylife").innerHTML =err.name;
           }

Certain functions in JavaScript have ranges of inputs that you can give. Always be careful of the ranges. Sometimes while scripting we use functions that in the end go out of range, while performing tasks. These errors can be easily tackled, if while implementation you keep track of the ranges of variable types used.

While modern browsers like Chrome and Firefox report the error in the console, the discontinued Internet Explorer used to crash outright instead of showing a message.

Opening a chrome debugger session on the failing page shows the exact line and call stack behind the RangeError.

It should be of utmost priority that you check the valid input ranges.

Examples:

Number.toFixed(digits) 0 to 100

Number.toPrecision(digits) 1 to 100

Number.toExponential(digits) 0 to 100

Null is not 0

These ranges were extended to a maximum of 100 digits; see MDN's toFixed() reference for the current limits.

Hopefully this blog will help coders a bit in their frustrating hard work.

Let us learn from your mistakes too, please comment.

function safeArray(length) {
  try {
    return new Array(length);
  } catch (err) {
    console.log(err.name, err.message);
    return [];
  }
}

safeArray(10);          // OK
safeArray(-1);          // RangeError, caught
safeArray(4294967296);  // RangeError, caught