Solution:Step 1: Analyze the codeCallbacks are stored indefinitely in an array without removal.Step 2: Understand impactAccumulating references prevent garbage collection, causing memory leaks.Final Answer:Memory leak due to accumulating unused callback references -> Option BQuick Check:Uncleared ar

[Solved] Examine this code:const storedCallbacks = []; function registerCallback(cb) { storedCallbacks.push(cb);... // storedCallbacks never cleared What memory problem does this cause? | Node.js

Node.js - Debugging and Profiling

Examine this code:

const storedCallbacks = [];
function registerCallback(cb) {
  storedCallbacks.push(cb);
}
registerCallback(() => console.log('Event'));
// storedCallbacks never cleared

What memory problem does this cause?

AStack overflow from recursive calls

BMemory leak due to accumulating unused callback references

CEvent emitter not emitting events

DSyntax error from invalid callback

Step-by-Step Solution

Solution:

Step 1: Analyze the code
Callbacks are stored indefinitely in an array without removal.
Step 2: Understand impact
Accumulating references prevent garbage collection, causing memory leaks.
Final Answer:
Memory leak due to accumulating unused callback references -> Option B
Quick Check:
Uncleared arrays cause leaks [OK]

Quick Trick: Never keep unused callbacks indefinitely [OK]

Common Mistakes:

Confusing memory leak with stack overflow
Assuming syntax errors cause leaks
Thinking event emission is affected

Master "Debugging and Profiling" in Node.js

9 interactive learning modes - each teaches the same concept differently

Learn Why Deep Visual Try Challenge Project Recall Perf

More Node.js Quizzes

Examine this code:

Step 1: Analyze the code

Step 2: Understand impact

Final Answer:

Quick Check:

Want More Practice?