extracted from #33803.
Previously debuggers would activate on the onDebug:type activation event which only fires if this type of debugging is really needed (e.g. because the user runs a launch config that refers to this debug type). So, a Java debug extension would not activate if the user only works in (and debugs) a Python project.
With the new debug API it has become necessary that debug extensions are activated as soon as any debugging functionality is triggered so that they can register their "DebugConfigurationProvider" for a specific debug type. For this we have introduced a onDebug activation event.
A consequence of this is that all debug extensions are activated as soon as a launch configuration is started (independent of type). As long as activation of a debug extension is cheap this is not a problem. However, there are some debug extensions where activation triggers a language server to start up which makes the original debug operation (that triggered the activation) behave sluggish.
We should find a way to mitigate this.
extracted from #33803.
Previously debuggers would activate on the
onDebug:typeactivation event which only fires if this type of debugging is really needed (e.g. because the user runs a launch config that refers to this debug type). So, a Java debug extension would not activate if the user only works in (and debugs) a Python project.With the new debug API it has become necessary that debug extensions are activated as soon as any debugging functionality is triggered so that they can register their "DebugConfigurationProvider" for a specific debug type. For this we have introduced a
onDebugactivation event.A consequence of this is that all debug extensions are activated as soon as a launch configuration is started (independent of type). As long as activation of a debug extension is cheap this is not a problem. However, there are some debug extensions where activation triggers a language server to start up which makes the original debug operation (that triggered the activation) behave sluggish.
We should find a way to mitigate this.