Extension causes high cpu load

[bkhouri]

• Issue Type: Performance
• Extension Name: swift-vscode
• Extension Version: 2.16.1 (pre-release)
• OS Version: Darwin arm64
• VS Code version: 1.108.2

swiftlang.swift-vscode-unresponsive.cpuprofile.txt

Find more details here: https://github.com/microsoft/vscode/wiki/Explain-extension-causes-high-cpu-load

Running the Swift: Capture Diagnostic Logs does nothing at the extension is still activating.

Here is the logs from the Swift output console

2026-02-03 15:21:26.833 [info] Activating Swift for Visual Studio Code 2.16.1...
2026-02-03 15:21:26.833 [info] Log setup completed in 1ms
2026-02-03 15:21:27.074 [info] Package search for swift-package-manager completed in 1ms (found 1 packages)
2026-02-03 15:21:27.668 [info] swift-package-manager: Describing Package: starting ... 
2026-02-03 15:21:27.668 [info] Exec Task: swift package describe --type json
2026-02-03 15:21:27.684 [info] swift-package-manager: workspaceStateUpdated: /Users/bkhouri/Documents/git/public/swiftlang/swift-package-manager
2026-02-03 15:21:27.691 [info] SourceKit-LSP setup
2026-02-03 15:21:27.691 [info] swift-package-manager: add: /Users/bkhouri/Documents/git/public/swiftlang/swift-package-manager
2026-02-03 15:21:27.755 [info] Project panel updating after task swift package describe --type json has started
2026-02-03 15:21:29.074 [info] Selected Xcode changed from undefined to /Applications/XcodeWE.app/Contents/Developer
2026-02-03 15:21:29.693 [info] swift-package-manager: Describing Package: ... done.

[MahdiBM]

I've also had to downgrade to 2.14. For me it'd get stuck in the "package describe", or at least that's what the extension status would say.

[matthewbastien]

@MahdiBM The extension in 2.16 should be showing the status of the swift package describe in the VS Code terminal as a task. Can you see if it's stuck on something?

[MahdiBM]

Tried the latest version again now, couldn't reproduce immediately. Will report back later if I can reproduce again.

[matthewbastien]

Tried the latest version again now, couldn't reproduce immediately. Will report back later if I can reproduce again.

I was able to reproduce it once on my Windows machine. Seems like the extension might be missing the timing on the task completion event. I think what you're seeing is actually a separate issue from this one. I'm looking into it.