Invisible, unspecified Breakpoint hit with no call stack

Not reproducible Issue #22400847

Details

Author
Sameera P.
Created
Jun 26, 2019
Privacy
This issue is public.
Found in
  • Microsoft Edge
  • Internet Explorer
Reports
Reported by 1 person

Sign in to watch or report this issue.

Steps to reproduce

Happens in Edge and IE F12 Developer Tools (standalone and embedded):

On certain Angular/TS Karama test projects, we would run in to these phantom breakpoints where Dev Tools seem to have hit a breakpoint, where there isn’t any (probably in non-user code), and will not proceed even after many many F5 presses.
There’s no callstack at this point or any other indication what the tools is waiting on.

Our only recourse after which, becomes using a different browser to test.

Attachments

Comments and activity

  • Hi Sameera!

    Could you provide me with a minimal reproduction for this issue?

    Thanks,
    Zach

  • Microsoft Edge Team

    Changed Assigned To to “Zachariah L.”

  • Hi Zach,
    Unfortunately, I don’t have a reliable repro of this issue. I’m running in to this on our code base right now. Generally this issue resolves itself after sometime (I’m guessing after more code or tests are added) and resurfaces at some later point.

  • Given that this is an Angular + TS code base, I would guess this has to do with changing source maps due to changes in code and recompilation. Before this happens, we’d typically see our existing breakpoints move to areas in code that were never set breakpoints (often times in to vendor.js).

  • Hi Sameera!

    In order for this issue to be actionable, we need to be able to reproduce the issue locally. Is there anything you could provide me to reproduce the issue here?

    Thanks,
    Zach

  • Hi Sameera!

    For now, I will resolve this issue as "Not Reproducible". If you are still experiencing this problem then please feel free to reopen this issue with the information requested and I will resume my investigation.

    Thanks,

    Zach

  • Microsoft Edge Team

    Changed Status to “Not reproducible”

You need to sign in to your Microsoft account to add a comment.

Sign in