# Debugger no longer hits breakpoints in VSC?

**URL:** <https://discourse.julialang.org/t/debugger-no-longer-hits-breakpoints-in-vsc/136161>\
**Category:** General Usage\
**Tags:** vscode, debugger\
**Created:** [March 12, 2026, 12:28pm UTC](https://discourse.julialang.org/t/debugger-no-longer-hits-breakpoints-in-vsc/136161 "2026-03-12T12:28:12Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![karei](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/karei/32/214809_2.png) [@karei](https://discourse.julialang.org/u/karei)\
**Post date:** [March 13, 2026, 8:19am UTC](https://discourse.julialang.org/t/debugger-no-longer-hits-breakpoints-in-vsc/136161/3 "2026-03-13T08:19:41Z")

</div>

> [@Julia debugging is extremely slow](https://discourse.julialang.org/t/julia-debugging-is-extremely-slow/135839/3):
>
> Well, you can select which libraries shall be compiled. If you are not debugging the CSV library, just compile it: [Debugging · Julia in VS Code](https://www.julia-vscode.org/docs/stable/userguide/debugging/#Settings-to-speed-up-the-debugger) You can also try [https://plugins.jetbrains.com/plugin/29356-flexible-julia](https://plugins.jetbrains.com/plugin/29356-flexible-julia), which is a commercial offering, so you need to pay for it unless you work at a university. On the other hand, if you have a bug report or feature request they address that very fast.

> [@Julia debugging is extremely slow](https://discourse.julialang.org/t/julia-debugging-is-extremely-slow/135839/2):
>
> I would recommend just using Infiltrator.jl and putting an @infiltrate everwhere you want to inspect variables, and remove all of them when you are done.

---

_[View the full topic](https://discourse.julialang.org/t/debugger-no-longer-hits-breakpoints-in-vsc/136161)._