Why does apply with too many arguments throw "Maximum call stack size exceeded"?

Question

In Chrome and Node, the following code throws an error:

function noop() {}
var a = new Array(1e6)
// Array[1000000]
noop.apply(null, a)
// Uncaught RangeError: Maximum call stack size exceeded

I understand why it might be a Bad Idea to pass 1 million arguments to a function, but can anyone explain why the error is Maximum call stack size exceeded instead of something more relevant?

(In case this seems frivolous, the original case was Math.max.apply(Math, lotsOfNumbers), which is a not-unreasonable way of getting the max number from an array.)

…because function arguments are stored on the stack?

Bergi
– Bergi

2017-02-16 02:18:27 +00:00
Commented Feb 16, 2017 at 2:18 — Bergi
– Bergi, Commented Feb 16, 2017 at 2:18
Well, yes, that's the piece of info I was missing :)

nrabinowitz
– nrabinowitz

2017-02-16 03:44:30 +00:00
Commented Feb 16, 2017 at 3:44 — nrabinowitz
– nrabinowitz, Commented Feb 16, 2017 at 3:44

Barmar · Accepted Answer · 2017-02-16 01:19:03Z

13

Function arguments are put on the stack. You're trying to put a million arguments onto the stack, and that's more than the maximum stack size. So the error message is very relevant to the reason for the error.

answered Feb 16, 2017 at 1:19

Barmar

789k57 gold badges555 silver badges669 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

chrispy Over a year ago

For anyone wanting more specific browser stack size limitations, I found this: stackoverflow.com/questions/7826992/…

Collectives™ on Stack Overflow

Why does apply with too many arguments throw "Maximum call stack size exceeded"?

1 Answer 1

1 Comment

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Your Answer

Sign up or log in

Post as a guest

Linked

Related