Welcome to the Treehouse Community

Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.

Start your free trial

Computer Science Introduction to Algorithms Recursion and Space Complexity Space Complexity

Andrew Whatmore
seal-mask
.a{fill-rule:evenodd;}techdegree
Andrew Whatmore
Full Stack JavaScript Techdegree Student 13,175 Points

JavaScript passing in copies of variables to functions

Since JavaScript passes in copies of variables as the arguments in function calls, does this make the use of recursion space-expensive, since new copies are made on each recursive call?

1 Answer

Laura Coronel
seal-mask
STAFF
.a{fill-rule:evenodd;}techdegree
Laura Coronel
Treehouse Teacher

Hi Andrew Whatmore Great question! You're right that each recursive call creates a new stack frame, which takes up memory. However, JavaScript doesn't necessarily copy the entire value of every argument.

For primitive values (like numbers and strings), the value is passed to the function. For objects and arrays, the reference is copied, not the entire object or array.

Recursion does have some memory overhead because each call stays on the call stack until it returns. So, deep recursion can use a lot of memory and may eventually cause a stack overflow. The amount of memory used depends on how many recursive calls are active and what each call needs to keep track of.