Chrome "Aw, Snap! Error code: 5" when stepping over a for loop breakpoint in Angular effect...

Discussão em 'Angular' iniciado por Yousaf Raza, Abril 10, 2025.

  1. Yousaf Raza

    Yousaf Raza Guest

    I'm working on an Angular application with NgRx and RxJS effects, and I'm running into a consistent issue when debugging a particular for loop.

    When I set a breakpoint directly on the for loop statement (inside an exhaustMap in an NgRx effect), and then hit "Step Over" in Chrome DevTools, the browser tab crashes with an "Aw, Snap! Something went wrong while displaying this webpage" message and Error Code: 5:

    [​IMG]

    What I've tried:


    • Moving the breakpoint inside the loop — works fine, no crash.


    • Stepping into instead of over — also works.


    • Updating Chrome to the latest version (still happens).


    • Disabling extensions.


    • Verified there are no infinite loops or memory issues.


    • Cleared cache and restarted browser.

    Environment:


    • Angular: 15+


    • RxJS: 7+


    • NgRx: 15


    • Chrome: Version 123.0.x (Mac M1)


    • OS: macOS Ventura

    It seems like stepping over a for loop keyword in this async-heavy context causes Chrome's V8/DevTools to crash. Maybe source maps or complex nesting (like exhaustMap) is making it worse.

    Questions:


    • Has anyone else encountered this crash (Error code: 5) specifically when breaking on for loops?


    • Is this a known DevTools issue?


    • Is there a workaround besides avoiding breakpoints on loop declarations?

    Continue reading...

Compartilhe esta Página