Uncaught RangeError: Maximum call stack in JavaScript

Posted by Robin Jangu | March 28, 2018
Debug β€’ JavaScript β€’ Miscellaneous β€’

3648 Views | 2 Min Read

Uncaught RangeError: Maximum call stack

Errors occur where you least expect them, JS developers face this nemesis on a daily basis.

There are 2 ways to get these wonderful error messages:

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)

2) Out of Range

If someone asks you what your name is.

You won’t reply β€˜2000 yrs’.

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 browsers like Chrome will give error notifications, IE will crash.

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

Examples:

Number.toFixed(digits) 0 to 20

Number.toPrecision(digits) 1 to 21

Number.toExponential(digits) 0 to 20

Null is not 0

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

Let us learn from your mistakes too, please comment.

Written by Robin Jangu

Related Articles

Leave a Reply

Your email address will not be published. Required fields are marked *