-
Notifications
You must be signed in to change notification settings - Fork 38.2k
Closed
Closed
Copy link
Labels
bugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bugdebugDebug viewlet, configurations, breakpoints, adapter issuesDebug viewlet, configurations, breakpoints, adapter issuesinsiders-releasedPatch has been released in VS Code InsidersPatch has been released in VS Code Insiderson-release-notesIssue/pull request mentioned in release notesIssue/pull request mentioned in release notesverifiedVerification succeededVerification succeeded
Milestone
Description
In 1.50, any extension that has onDebugDynamicConfigurations in its activation events is immediately activated when opening any project loading VS Code. This did not happen in v1.49.
[2020-10-13 10:37:47.815] [exthost] [info] ExtensionService#_doActivateExtension Dart-Code.dart-code {"startup":false,"extensionId":{"value":"Dart-Code.dart-code","_lower":"dart-code.dart-code"},"activationEvent":"onDebugDynamicConfigurations"}
There's some discussion around this in #96297 / #88230 and my understanding is that they should not be activated so early. This leads to other issues such as language extensions spawning their language servers for every project (whether they should is another issue - but there's no guidance from VS Code on how they should handle this, especially without knowing why they were activated).
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bugdebugDebug viewlet, configurations, breakpoints, adapter issuesDebug viewlet, configurations, breakpoints, adapter issuesinsiders-releasedPatch has been released in VS Code InsidersPatch has been released in VS Code Insiderson-release-notesIssue/pull request mentioned in release notesIssue/pull request mentioned in release notesverifiedVerification succeededVerification succeeded