Which garbage collection approach is most likely to cause noticeable pauses in interactive applications?
Stop-the-world garbage collection is most likely to cause noticeable pauses: 1) It completely halts program execution while the garbage collector runs, 2) This pauses all JavaScript execution, including UI updates and event handling, 3) Users may experience jarring stutters or freezes during these collection cycles, 4) The pause duration grows with heap size and complexity, 5) Modern JavaScript engines have worked to minimize these pauses through other approaches, 6) Incremental GC breaks the collection into smaller steps to reduce pause times, 7) Concurrent GC performs most work alongside program execution, 8) Generational GC focuses collection efforts on newer objects to improve efficiency, but doesn't inherently determine whether collection is stop-the-world or concurrent.