Extension causes high cpu load

[NikhileshPatilMSD]

• Issue Type: Performance
• Extension Name: vscode-azurelogicapps
• Extension Version: 5.991.3
• OS Version: Windows_NT x64 10.0.26200
• VS Code version: 1.133.0

⚠️ Make sure to attach this file from your home-directory:
⚠️file:///c%3A/Users/****/AppData/Local/Temp/ms-azuretools.vscode-azurelogicapps-unresponsive.cpuprofile.txt

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

[github-actions]

AI Triage Analysis

Component: VSCode Extension | Priority: P3 - Medium | SKU: Standard (VSCode)

Relevant Code

• apps/vs-code-designer/src/app/commands/workflows/overview/panels/overviewPanel.ts — Contains startPollingInterval() which calls setInterval(..., 5000) to poll access tokens, base URLs, and callback info every 5 seconds while an Overview panel is open
• apps/vs-code-designer/src/app/languageServer/languageServer.ts — Starts a .NET LSP server process (via LanguageClient) with a FileSystemWatcher on all *.cs files; this background process could contribute to CPU overhead

Probable Root Cause

The extension's Overview panel polling loop (setInterval at 5-second intervals) makes async network calls (pollAccessToken, pollBaseUrl, handleCallbackInfoUpdate) that may accumulate if responses are slow or panels aren't disposed. Separately, the Language Server process (a .NET executable) is spawned on workspace open for C# workflow authoring and syncs file changes continuously via workspace.createFileSystemWatcher('**/*.cs'). Either or both could show up as high CPU in a profile, especially with multiple workflows open or in a large workspace. The CPU profile attached by the reporter should confirm which call stack dominates.

Suggested Investigation

1. Open the attached .cpuprofile.txt in VS Code's CPU profiler viewer (or Chrome DevTools) and identify the top hot call stacks — confirm whether they originate in overviewPanel.ts's poll callbacks or from the Language Server process.
2. Check if the high CPU persists when no Overview panel is open (closing all overview panels stops the setInterval via dispose()). If CPU drops, the polling loop is the primary cause.
3. Evaluate whether the FileSystemWatcher('**/*.cs') in languageServer.ts is scanning a large workspace without exclusions, which could cause excessive FS events.

---

Automated analysis by issue triage agent. May contain inaccuracies — verify before acting.
Calibration: reviewed 10 past triages, 0 corrections found (no prior triage comments from this agent).

Generated by Issue Triage Agent for Azure Logic Apps UX for #9540 · sonnet46 36.5 AIC · ⌖ 5.19 AIC · ⊞ 11.1K · ◷

[lambrianmsft]

Nikhilesh Patil (@NikhileshPatilMSD) Please upload the CPU Profile for us to inspect! This is found in the following location

⚠️ Make sure to attach this file from your home-directory:
⚠️file:///c%3A/Users/****/AppData/Local/Temp/ms-azuretools.vscode-azurelogicapps-unresponsive.cpuprofile.txt