JavaScript Interview Questions
  • JavaScript Interview Questions
  • Contact
  • Introduction
  • Question 1
  • Question 2
  • Question 3
  • Question 4
  • Question 5
  • Question 6
  • Question 7
  • Question 8
  • Question 9
  • Question 10
  • Question 11
  • Question 12
  • Question 13
  • Question 14
  • Question 15
  • Question 16
  • Question 17
  • Question 18
  • Question 19
  • Question 20
  • Question 21
  • Question 22
  • Question 23
  • Question 24
  • Question 25
  • Question 26
  • Question 27
  • Question 28
  • Question 29
  • Question 30
  • Question 31
  • Question 32
  • Question 33
  • Question 34
  • Question 35
  • Question 36
  • Question 37
  • Question 38
  • Question 39
  • Question 40
  • Question 41
  • Question 42
  • Question 43
  • Question 44
  • Question 45
  • Question 46
  • Question 47
  • Question 48
  • Question 49
  • Question 50
  • Question 51
  • Question 52
  • Question 53
  • Question 54
  • Question 55
  • Question 56
  • Question 57
  • Question 58
  • Question 59
  • Question 60
  • Question 61
  • Question 62
  • Question 63
  • Question 64
  • Question 65
  • Question 66
  • Question 67
  • Question 68
  • Question 69
  • Question 70
  • Question 71
  • Question 72
  • Question 73
  • Question 74
  • Question 75
  • Question 76
  • Question 77
  • Question 78
  • Question 79
  • Question 80
  • Question 81
  • Question 82
  • Question 83
  • Question 84
  • Question 85
  • Question 86
  • Question 87
  • Question 88
  • Question 89
  • Question 90
  • Question 91
  • Question 92
  • Question 93
  • Question 94
  • Question 95
  • Question 96
  • Question 97
  • Question 98
  • Question 99
  • Question 100
  • Epilogue
Powered by GitBook
On this page
  • Question
  • Answer

Question 90

Question

How does JavaScript's event loop handle microtasks vs macrotasks?

Answer

JavaScript's event loop is the heart of its asynchronous nature, managing how tasks are executed and ensuring a smooth user experience. Understanding how it handles different types of tasks, specifically microtasks and macrotasks, is crucial for writing efficient and responsive code.

1. Microtasks:

  • Purpose: Microtasks represent small, lightweight operations that usually occur within the web browser's event loop. They are often associated with asynchronous operations like setting up timers (setTimeout, setInterval) or handling tasks deferred by Promises (then callbacks).

  • Execution:

    • Microtasks are always executed before macrotasks in each iteration of the event loop. This means that they have higher priority.

2. Macrotasks:

  • Purpose: Macrotasks encompass a wider range of operations, including:

    • Code execution from scripts.

    • Handling user interactions (e.g., button clicks).

    • Processing DOM manipulations.

  • Execution:

    • Macrotasks are executed after all microtasks have been processed in the current event loop iteration.

The Flow:

  1. A macrotask is initiated (e.g., a user clicks a button).

  2. The JavaScript engine pushes the macrotask onto the "Call Stack" – where tasks are actively being executed.

  3. While the macrotask is running, it might trigger asynchronous operations (e.g., fetching data from a server) which create microtasks.

  4. Once the current macrotask completes, the Call Stack becomes empty.

  5. The JavaScript engine then checks the "Microtask Queue." If there are any microtasks waiting, they are executed one by one until the queue is empty.

  6. Finally, if there are more macrotasks in the "Task Queue," a new macrotask is picked up and pushed onto the Call Stack, restarting the cycle.

Illustrative Example:

console.log("Start"); // Macrotask 1

setTimeout(() => {
  console.log("Microtask"); // Microtask
}, 0); // Schedule a microtask to run after the current macrotask

console.log("End"); // Macrotask 2

Output:

Start
End
Microtask

In this example, "Start" and "End" are macrotasks. setTimeout creates a microtask that executes after both macrotasks are complete.

PreviousQuestion 89NextQuestion 91

Last updated 9 months ago