Call stack behavior in Javascript - Time & Space Complexity

Time Complexity: Call stack behavior

O(n)

Understanding Time Complexity

When functions call other functions, the call stack keeps track of them. Understanding how this stack grows helps us see how the program's work increases.

We want to know how the number of function calls affects the total steps the program takes.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

function countdown(n) {
  if (n <= 0) return;
  countdown(n - 1);
}

countdown(5);
    

This code calls itself repeatedly, counting down from n to 1.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Recursive function calls to countdown.
• How many times: Exactly n times, once for each number down to one.

How Execution Grows With Input

Each time n increases by 1, the function calls itself one more time.

Input Size (n)	Approx. Operations
10	10 calls
100	100 calls
1000	1000 calls

Pattern observation: The number of calls grows directly with n, so doubling n doubles the work.

Final Time Complexity

Time Complexity: O(n)

This means the total steps grow in a straight line with the input size.

Common Mistake

[X] Wrong: "Recursive calls happen all at once, so time stays the same no matter n."

[OK] Correct: Each call waits for the next one to finish, so calls add up one after another, increasing total time.

Interview Connect

Understanding how the call stack grows with recursion helps you explain function behavior clearly and shows you can think about program steps carefully.

Self-Check

"What if countdown called itself twice each time? How would the time complexity change?"

Practice

1. What does the call stack do in JavaScript?

easy

A. Keeps track of function calls in the order they are called

B. Stores variables and their values

C. Manages asynchronous events

D. Handles network requests

Solution

1. Step 1: Understand the role of the call stack

   The call stack tracks which functions are currently running and in what order.

2. Step 2: Differentiate from other JavaScript components

   Variables are stored in memory, asynchronous events are handled by the event loop, and network requests are managed separately.

3. Final Answer:

   Keeps track of function calls in the order they are called -> Option A

4. Quick Check:

   Call stack = function order tracking [OK]

Hint: Call stack = function call order tracker [OK]

Common Mistakes:

• Confusing call stack with event loop
• Thinking call stack stores variables
• Mixing call stack with network handling

2. Which of the following is the correct way to call a function named foo in JavaScript?

easy

A. call foo();

B. function foo();

C. execute foo();

D. foo();

Solution

1. Step 1: Recall JavaScript function call syntax

   Functions are called by writing their name followed by parentheses, like foo();.

2. Step 2: Identify incorrect options

   "call foo();" and "execute foo();" are not valid JavaScript syntax. "function foo();" is a function declaration, not a call.

3. Final Answer:

   foo(); -> Option D

4. Quick Check:

   Function call = name + () [OK]

Hint: Call functions with name and parentheses () [OK]

Common Mistakes:

• Using 'call' keyword incorrectly
• Confusing declaration with call
• Adding extra keywords like 'execute'

3. What will be the output of the following code?

function first() {
  console.log('first');
  second();
  console.log('first again');
}

function second() {
  console.log('second');
}

first();

medium

A. second\nfirst\nfirst again

B. first\nsecond\nfirst again

C. first\nfirst again\nsecond

D. first again\nsecond\nfirst

Solution

1. Step 1: Trace the call stack execution order

   Calling first() prints 'first', then calls second() which prints 'second'. After second() finishes, control returns to first() and prints 'first again'.

2. Step 2: Confirm output sequence

   The output lines are: 'first', 'second', 'first again' in that order.

3. Final Answer:

   first second first again -> Option B

4. Quick Check:

   Call stack order = first, second, first again [OK]

Hint: Follow function calls step-by-step [OK]

Common Mistakes:

• Assuming all logs run before second()
• Mixing order of console logs
• Ignoring return to first() after second()

4. Identify the error in the following code related to call stack behavior:

function a() {
  b();
}

function b() {
  a();
}

a();

medium

A. Function b is not defined

B. Syntax error due to missing semicolons

C. Infinite recursion causing stack overflow

D. No error, code runs fine

Solution

1. Step 1: Analyze function calls and recursion

   Function a() calls b(), and b() calls a() again, creating an endless loop.

2. Step 2: Understand call stack impact

   This infinite mutual recursion causes the call stack to grow until it overflows, leading to a runtime error.

3. Final Answer:

   Infinite recursion causing stack overflow -> Option C

4. Quick Check:

   Mutual recursion without stop = stack overflow [OK]

Hint: Watch for functions calling each other endlessly [OK]

Common Mistakes:

• Thinking missing semicolons cause error
• Assuming functions are undefined
• Believing code runs without error

5. Consider this code:

function factorial(n) {
  if (n === 0) return 1;
  return n * factorial(n - 1);
}

console.log(factorial(3));

How many times is the factorial function added to the call stack during factorial(3) execution?

hard

A. 4 times

B. 6 times

C. 1 time

D. 3 times

Solution

1. Step 1: Trace recursive calls for factorial(3)

   Calls happen for n=3, n=2, n=1, and n=0. Each call adds a new frame to the call stack.

2. Step 2: Count total calls added to the stack

   There are 4 calls total before reaching the base case (n=0), so 4 stack frames are added.

3. Final Answer:

   4 times -> Option A

4. Quick Check:

   Recursive calls = n+1 stack frames [OK]

Hint: Count calls including base case for recursion [OK]

Common Mistakes:

• Counting only n times, missing base case call
• Confusing total calls with return steps
• Assuming single call for recursion