VSCode Extension Host Keeps Crashing As Soon as First Project is Added

RE: VSCode Extension Host Keeps Crashing As Soon as First Project is Added

Toastus — Thu, 29 Jan 2026 00:15:12 GMT

I hit this similarly on an M1 MacBook Air just today. I've been doing most of my development on an M4 MacMini and never saw this, but had moved development over to the MacBook due to potential power loss due to winter storms.

I see evidence of high memory pressure on the M1 Air, probably because it only has 8GB RAM vs. the M4 Mini's 16GB, but the problem started happening when I was working with devicetree, and if I disable the nRF Devicetree extension (version 2026.1.448), the problem disappears, but so do the devicetree related features, such as listing the specific build target systems in the nRF Connect Applications sidebar, for example. Note that since I hit the issue, I've been working editing application source, not device tree, but the error persists.

I found that this was the cause by digging into the error logs generated by the Extensions Host--it was holding onto the CPU and unresponsive for 81% of almost 5 seconds at a time, which caused the Host to crash, so it's possible that memory and/or system speed plus aggressive crash timing by the Extensions Host is involved, which would explain why the exact same cloned environment does not experience any issues on the M4 Mini.

Update: Removing the nRF Devicetree Extension then fully closing VS Code, then reopening VS Code and Installing the extension again seems to have cleared up the issue.

RE: VSCode Extension Host Keeps Crashing As Soon as First Project is Added

brunohaid — Tue, 20 Jan 2026 10:33:35 GMT

Completely fresh install on new machine with latest version as per docs. Bisect doesn't work, but deactivating nrfSDK in VSCode is what prevents the error.

Again, my assumption is that the way you scan the repo leads to some infinite/recursive issue exhausting system memory, last year it looked like you were using the standard C/C++ plugin in some specific ways under the hood.

RE: VSCode Extension Host Keeps Crashing As Soon as First Project is Added

Priyanka — Tue, 20 Jan 2026 09:51:43 GMT

Hi,

Thank you for the inputs, but we are still not able to reproduce it at our end.

This is a pretty old ticket, and since the first report, there have been a lot of updates on various stuff like the VSCode versions, toolchains, JLinks, etc etc. Please make sure that you have updated everything to the latest versions.

You can also use the following to narrow it down to the extension that creates this issue:

-Priyanka

RE: VSCode Extension Host Keeps Crashing As Soon as First Project is Added

brunohaid — Sun, 11 Jan 2026 01:34:11 GMT

Tried giving the SDK a shot again, but this got significantly worse - it now somehow manages to crash VS Code in way that leaves the process in an UE state (uninterruptable, trying to exit), which means the only way to restart VS Code is by literally restarting your computer. The old trick of setting Intellisense cache size to 0 also doesn't work anymore.

Bit weird to see this thread abandoned by the support team.

RE: VSCode Extension Host Keeps Crashing As Soon as First Project is Added

mbprx — Thu, 15 May 2025 00:16:21 GMT

No luck for me either :( just suffering. I thought it might have been a conflict with the Cmake tools extension, but I think the error messages I saw there were collateral damage of whatever underlying issue is present here.

RE: VSCode Extension Host Keeps Crashing As Soon as First Project is Added

brunohaid — Tue, 13 May 2025 22:09:43 GMT

Unfortunately not. We did have some success with "C_Cpp.intelliSenseCacheSize": 0 in settings.json stopping the underlying extension from being told to run amok (similar to this issue) and produce terabyte sized cache files saturating discs. It does help, in combination with

"C_Cpp.exclusionPolicy": "checkFolders",
"C_Cpp.files.exclude": {
"${workspaceFolder}/lib/**": true
...
},
"files.watcherExclude": {
"${workspaceFolder}/lib/**": true

...
},

but at that point you're starting to defeat the purpose of having VS Code for your development in the first place. Given that it's also near impossible to have NCS and CLI/West builds coexist we stopped investigating the issue and scrapped using the NCS VS Code plugins altogether.

As a heavy VS Code user and embedded n00b, this seemed annoying initially but turned out OK - Similar to the ST IDE you can always spin up a quick isolated project to learn/develop/test something, and then transfer it over to your main codebase. Plus you get to feel closer closer to the VIM/CLI cool kids on your team..

RE: VSCode Extension Host Keeps Crashing As Soon as First Project is Added

Andre Petronilho — Tue, 13 May 2025 20:39:32 GMT

Did anyone figured this out? I am having the same issue with my Mac M1 and SDK3.0.0.

RE: VSCode Extension Host Keeps Crashing As Soon as First Project is Added

Ramiws — Mon, 17 Mar 2025 14:38:32 GMT

I am also facing the crash of the extension every couple of minutes. I am also on Mac M2 and sdk 2.9.0

This is the crash message. Not very helpful:

Extension host terminated unexpectedly 3 times within the last 5 minutes.

RE: VSCode Extension Host Keeps Crashing As Soon as First Project is Added

mbprx — Thu, 06 Feb 2025 18:42:40 GMT

Unfortunately no luck with 2.9.99.

My steps to reproduce:

Create a blank application via VS Code extension (this is a freestanding application that uses the SDK / toolchain that are downloaded and managed by the extension)
Create a simple build configuration that uses SDK v2.9.0 (or v2.9.99)
Wait ~5 mins and the extension host will restart at some point

I typically go on to flash and monitor the nRF54L15 DK via serial, but in my experience I only need to create a build configuration & build to get the extension host to crash.

I'm having a hard time finding smoke in the VS Code logs, but here's a session where I opened VS Code, promptly built, flashed, and then the extension host rebooted.

main.log

2025-02-06 12:57:16.749 [info] update#setState idle
2025-02-06 12:57:46.746 [info] update#setState checking for updates
2025-02-06 12:57:47.202 [info] update#setState idle
2025-02-06 13:01:06.279 [info] Extension host with pid 58325 exited with code: 6, signal: unknown.
2025-02-06 13:01:06.280 [error] [UtilityProcess id: 1, type: extensionHost, pid: 58325]: crashed with code 6 and reason 'crashed'
2025-02-06 13:04:22.537 [info] Extension host with pid 60724 exited with code: 6, signal: unknown.
2025-02-06 13:04:22.537 [error] [UtilityProcess id: 2, type: extensionHost, pid: 60724]: crashed with code 6 and reason 'crashed'

exthost.log

2025-02-06 12:57:17.574 [info] Extension host with pid 58325 started
2025-02-06 12:57:17.574 [info] Skipping acquiring lock for /Users/miles/Library/Application Support/Code/User/workspaceStorage/1d4775150777675da9dcbff7125bca9c.
2025-02-06 12:57:17.625 [info] ExtensionService#_doActivateExtension vscode.github-authentication, startup: false, activationEvent: 'onAuthenticationRequest:github'
2025-02-06 12:57:17.656 [info] ExtensionService#_doActivateExtension vscode.git-base, startup: true, activationEvent: '*', root cause: vscode.git
2025-02-06 12:57:17.658 [info] ExtensionService#_doActivateExtension nordic-semiconductor.nrf-connect-extension-pack, startup: true, activationEvent: '*'
2025-02-06 12:57:17.659 [info] ExtensionService#_doActivateExtension nordic-semiconductor.nrf-kconfig, startup: true, activationEvent: '*'
2025-02-06 12:57:17.728 [info] ExtensionService#_doActivateExtension nordic-semiconductor.nrf-terminal, startup: true, activationEvent: '*'
2025-02-06 12:57:17.822 [info] ExtensionService#_doActivateExtension vscode.git, startup: true, activationEvent: '*'
2025-02-06 12:57:17.856 [info] ExtensionService#_doActivateExtension vscode.github, startup: true, activationEvent: '*'
2025-02-06 12:57:17.890 [info] ExtensionService#_doActivateExtension nordic-semiconductor.nrf-connect, startup: true, activationEvent: 'workspaceContains:**/west.yml,**/Kconfig.zephyr,**/prj.conf,**/*.overlay,**/sample.yaml'
2025-02-06 12:57:18.147 [info] ExtensionService#_doActivateExtension nordic-semiconductor.nrf-devicetree, startup: false, activationEvent: 'api', root cause: nordic-semiconductor.nrf-connect
2025-02-06 12:57:18.271 [info] ExtensionService#_doActivateExtension vscode.emmet, startup: false, activationEvent: 'onLanguage'
2025-02-06 12:57:19.901 [info] ExtensionService#_doActivateExtension ms-vscode.cpptools, startup: false, activationEvent: 'api', root cause: nordic-semiconductor.nrf-connect
2025-02-06 12:57:20.124 [info] Eager extensions activated
2025-02-06 12:57:20.129 [info] ExtensionService#_doActivateExtension vscode.debug-auto-launch, startup: false, activationEvent: 'onStartupFinished'
2025-02-06 12:57:20.130 [info] ExtensionService#_doActivateExtension vscode.merge-conflict, startup: false, activationEvent: 'onStartupFinished'
2025-02-06 13:01:06.640 [info] Extension host with pid 60724 started
2025-02-06 13:01:06.640 [info] Skipping acquiring lock for /Users/miles/Library/Application Support/Code/User/workspaceStorage/1d4775150777675da9dcbff7125bca9c.
2025-02-06 13:01:06.645 [info] ExtensionService#_doActivateExtension vscode.github-authentication, startup: false, activationEvent: 'onAuthenticationRequest:github'
2025-02-06 13:01:06.659 [info] ExtensionService#_doActivateExtension vscode.emmet, startup: false, activationEvent: 'onLanguage'
2025-02-06 13:01:06.668 [info] ExtensionService#_doActivateExtension nordic-semiconductor.nrf-connect, startup: false, activationEvent: 'onCommand:nrf-connect.getBuildEnvironment'
2025-02-06 13:01:06.802 [info] ExtensionService#_doActivateExtension ms-vscode.cpptools, startup: false, activationEvent: 'onLanguage:c'
2025-02-06 13:01:06.867 [info] ExtensionService#_doActivateExtension vscode.git-base, startup: false, activationEvent: 'onFileSystem:git', root cause: vscode.git
2025-02-06 13:01:06.868 [info] ExtensionService#_doActivateExtension nordic-semiconductor.nrf-terminal, startup: false, activationEvent: 'onCommand:nrf-terminal.startTerminal'
2025-02-06 13:01:06.985 [info] ExtensionService#_doActivateExtension vscode.git, startup: false, activationEvent: 'onFileSystem:git'
2025-02-06 13:01:07.133 [info] ExtensionService#_doActivateExtension nordic-semiconductor.nrf-kconfig, startup: false, activationEvent: 'api', root cause: nordic-semiconductor.nrf-connect
2025-02-06 13:01:07.192 [info] ExtensionService#_doActivateExtension nordic-semiconductor.nrf-devicetree, startup: false, activationEvent: 'api', root cause: nordic-semiconductor.nrf-connect
2025-02-06 13:01:07.646 [info] ExtensionService#_doActivateExtension vscode.github, startup: true, activationEvent: '*'
2025-02-06 13:01:07.660 [info] ExtensionService#_doActivateExtension nordic-semiconductor.nrf-connect-extension-pack, startup: true, activationEvent: '*'
2025-02-06 13:01:09.797 [info] Eager extensions activated
2025-02-06 13:01:09.798 [info] ExtensionService#_doActivateExtension vscode.debug-auto-launch, startup: false, activationEvent: 'onStartupFinished'
2025-02-06 13:01:09.801 [info] ExtensionService#_doActivateExtension vscode.merge-conflict, startup: false, activationEvent: 'onStartupFinished'
2025-02-06 13:04:22.962 [info] Extension host with pid 61517 started
2025-02-06 13:04:22.962 [info] Skipping acquiring lock for /Users/miles/Library/Application Support/Code/User/workspaceStorage/1d4775150777675da9dcbff7125bca9c.
2025-02-06 13:04:22.967 [info] ExtensionService#_doActivateExtension vscode.github-authentication, startup: false, activationEvent: 'onAuthenticationRequest:github'
2025-02-06 13:04:22.982 [info] ExtensionService#_doActivateExtension vscode.emmet, startup: false, activationEvent: 'onLanguage'
2025-02-06 13:04:22.991 [info] ExtensionService#_doActivateExtension nordic-semiconductor.nrf-connect, startup: false, activationEvent: 'onCommand:nrf-connect.getBuildEnvironment'
2025-02-06 13:04:23.120 [info] ExtensionService#_doActivateExtension ms-vscode.cpptools, startup: false, activationEvent: 'onLanguage:c'
2025-02-06 13:04:23.186 [info] ExtensionService#_doActivateExtension vscode.git-base, startup: false, activationEvent: 'onFileSystem:git', root cause: vscode.git
2025-02-06 13:04:23.189 [info] ExtensionService#_doActivateExtension nordic-semiconductor.nrf-terminal, startup: false, activationEvent: 'onCommand:nrf-terminal.startTerminal'
2025-02-06 13:04:23.309 [info] ExtensionService#_doActivateExtension vscode.git, startup: false, activationEvent: 'onFileSystem:git'
2025-02-06 13:04:23.467 [info] ExtensionService#_doActivateExtension nordic-semiconductor.nrf-kconfig, startup: false, activationEvent: 'api', root cause: nordic-semiconductor.nrf-connect
2025-02-06 13:04:23.526 [info] ExtensionService#_doActivateExtension nordic-semiconductor.nrf-devicetree, startup: false, activationEvent: 'api', root cause: nordic-semiconductor.nrf-connect
2025-02-06 13:04:23.972 [info] ExtensionService#_doActivateExtension vscode.github, startup: true, activationEvent: '*'
2025-02-06 13:04:23.987 [info] ExtensionService#_doActivateExtension nordic-semiconductor.nrf-connect-extension-pack, startup: true, activationEvent: '*'
2025-02-06 13:04:26.559 [info] Eager extensions activated
2025-02-06 13:04:26.561 [info] ExtensionService#_doActivateExtension vscode.debug-auto-launch, startup: false, activationEvent: 'onStartupFinished'
2025-02-06 13:04:26.563 [info] ExtensionService#_doActivateExtension vscode.merge-conflict, startup: false, activationEvent: 'onStartupFinished'

1-nRF Connect.log

[12:57:20] nRF Command Line Tools 10.24.2 are up to date
[12:57:20] =========== Toolchain validation report for nRF Connect SDK Toolchain v2.9.0 ===========
📦 Using the nRF Connect SDK v2.9.99 at /opt/nordic/ncs/main
No issues were detected with the toolchain.
[12:59:54] west build --build-dir /Users/miles/Documents/local_prx/repositories/internal/temp/temp_a/build /Users/miles/Documents/local_prx/repositories/internal/temp/temp_a --pristine --board nrf54l15dk/nrf54l15/cpuapp/ns -- -DNCS_TOOLCHAIN_VERSION=NONE
[13:00:17] Success.
[13:00:21] west flash -d /Users/miles/Documents/local_prx/repositories/internal/temp/temp_a/build --dev-id 1057721221
[13:00:25] Success.
[13:00:28] nrfutil-device --json device-info --serial-number 001057721221 --skip-overhead
[13:00:29] Success.

renderer.log

2025-02-06 12:57:17.027 [warning] Via 'product.json#extensionEnabledApiProposals' extension 'ms-vscode.vscode-selfhost-test-provider' wants API proposal 'attributableCoverage' but that proposal DOES NOT EXIST. Likely, the proposal has been finalized (check 'vscode.d.ts') or was abandoned.
2025-02-06 12:57:17.027 [warning] Via 'product.json#extensionEnabledApiProposals' extension 'ms-python.python' wants API proposal 'contribIssueReporter' but that proposal DOES NOT EXIST. Likely, the proposal has been finalized (check 'vscode.d.ts') or was abandoned.
2025-02-06 12:57:17.027 [warning] Via 'product.json#extensionEnabledApiProposals' extension 'ms-python.debugpy' wants API proposal 'contribIssueReporter' but that proposal DOES NOT EXIST. Likely, the proposal has been finalized (check 'vscode.d.ts') or was abandoned.
2025-02-06 12:57:17.027 [warning] Via 'product.json#extensionEnabledApiProposals' extension 'redhat.java' wants API proposal 'documentPaste' but that proposal DOES NOT EXIST. Likely, the proposal has been finalized (check 'vscode.d.ts') or was abandoned.
2025-02-06 12:57:17.220 [info] Started local extension host with pid 58325.
2025-02-06 12:57:17.682 [info] Settings Sync: Account status changed from uninitialized to unavailable
2025-02-06 12:57:19.845 [error] Error while getting the latest version for the extension twxs.cmake. Failed to fetch
2025-02-06 12:57:19.845 [error] Error while getting the latest version for the extension ms-vscode.cmake-tools. Failed to fetch
2025-02-06 12:57:19.859 [info] [perf] Render performance baseline is 15ms
2025-02-06 12:57:19.881 [error] Error while getting the latest version for the extension nordic-semiconductor.nrf-kconfig. Failed to fetch
2025-02-06 12:57:20.045 [error] Error while getting the latest version for the extension nordic-semiconductor.nrf-terminal. Unexpected HTTP response: 429
2025-02-06 13:01:06.283 [error] Extension host (LocalProcess pid: 58325) terminated unexpectedly. The following extensions were running: vscode.github-authentication, vscode.git-base, nordic-semiconductor.nrf-connect-extension-pack, nordic-semiconductor.nrf-kconfig, nordic-semiconductor.nrf-terminal, vscode.git, vscode.github, nordic-semiconductor.nrf-connect, nordic-semiconductor.nrf-devicetree, vscode.emmet, ms-vscode.cpptools, vscode.debug-auto-launch, vscode.merge-conflict
2025-02-06 13:01:06.284 [info] Automatically restarting the extension host.
2025-02-06 13:01:06.343 [info] Started local extension host with pid 60724.
2025-02-06 13:03:28.904 [error] TreeError [DebugRepl] Tree input not set: Error: TreeError [DebugRepl] Tree input not set
    at xf.C (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:412:29043)
    at xf.updateChildren (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:412:28950)
    at wte.value (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:2036:33515)
    at x.B (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:29:2392)
    at x.C (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:29:2462)
    at x.fire (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:29:2680)
    at uwe.setVisible (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:521:2801)
    at vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:749:11857
    at Array.map (<anonymous>)
    at Qh.setVisible (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:749:11848)
2025-02-06 13:04:22.540 [error] Extension host (LocalProcess pid: 60724) terminated unexpectedly. The following extensions were running: vscode.github-authentication, vscode.git-base, nordic-semiconductor.nrf-connect-extension-pack, nordic-semiconductor.nrf-kconfig, nordic-semiconductor.nrf-terminal, vscode.git, vscode.github, nordic-semiconductor.nrf-connect, nordic-semiconductor.nrf-devicetree, vscode.emmet, ms-vscode.cpptools, vscode.debug-auto-launch, vscode.merge-conflict
2025-02-06 13:04:22.541 [info] Automatically restarting the extension host.
2025-02-06 13:04:22.615 [info] Started local extension host with pid 61517.
2025-02-06 13:07:34.354 [error] Extension host (LocalProcess pid: 61517) terminated unexpectedly. The following extensions were running: vscode.github-authentication, vscode.git-base, nordic-semiconductor.nrf-connect-extension-pack, nordic-semiconductor.nrf-kconfig, nordic-semiconductor.nrf-terminal, vscode.git, vscode.github, nordic-semiconductor.nrf-connect, nordic-semiconductor.nrf-devicetree, vscode.emmet, ms-vscode.cpptools, vscode.debug-auto-launch, vscode.merge-conflict
2025-02-06 13:07:34.355 [info] Automatically restarting the extension host.
2025-02-06 13:07:34.415 [info] Started local extension host with pid 62757.

I'm not sure how helpful these are, so if there's a way I can get better diagnostic info please let me know. I'm still pretty new to NCS.

Thanks!

RE: VSCode Extension Host Keeps Crashing As Soon as First Project is Added

Priyanka — Thu, 06 Feb 2025 11:46:53 GMT

Hi,

Could you also try the v2.9.99 SDK and see if your issue is resolved? If not, please share the support log. Are there simple steps we can follow? Any peculiar detail about the environment, VSCode and west workspace structure would also help.

-Priyanka

RE: VSCode Extension Host Keeps Crashing As Soon as First Project is Added

brunohaid — Wed, 05 Feb 2025 23:10:39 GMT

The latest 2.9.99 SDK that was released a couple of hours ago seems to have resolved the issue for me - same on your end?

RE: VSCode Extension Host Keeps Crashing As Soon as First Project is Added

mbprx — Wed, 05 Feb 2025 02:40:44 GMT

Glad to hear I'm not the only one! Thought I was going crazy...

I've been experiencing the same thing for a couple months now, seems like the extension host crashes every ~60-180sec. It seems to dramatically slow down in the several seconds prior to crash.

So far, I had also tried a full VS Code reinstall with only the nRF Connect for VS Code Extension Pack installed but that resulted in the same behavior. I'm on an M1 mac and use freestanding applications.

The only interesting thing that I'd also note, is that the host only seems to crash after I've built an application. For example, if I create a new blank application using the extension, I can use the extension to view serial output from my DK indefinitely. However, as soon as I create and build a new configuration in the new application, the extension host will crash a few minutes later, along with the serial terminal.

RE: VSCode Extension Host Keeps Crashing As Soon as First Project is Added

brunohaid — Mon, 03 Feb 2025 14:15:26 GMT

Neither of them is, as mentioned firmware is our monorepo for all firmware development. It contains about 20 different projects, 4 of which are freestanding zephyr projects, two of them Nordic based, two STM32.

The two West workspaces are in lib/zephyr (latest Zephyr 4.0…) and lib/nordic (latest Nordic fork).

The Nordic one works with nrfutil, the latest Zephyr one with venv, as is recommended by Zephyr and works as it should. The zephyr sdk 0.17.0 is needed and used for building STM32 based zephyr projects.

All builds work, it’s just the VSCode Extension that keeps crashing.

RE: VSCode Extension Host Keeps Crashing As Soon as First Project is Added

Priyanka — Mon, 03 Feb 2025 13:55:59 GMT

From the logs we don't see that the firmware directory or the application in it would be a west workspace.

I assume that it is a "freestanding" application. In that case it's also a bit unusual that the "SDK"s i.e. lib/nordic and lib/zephyr are under this directory - We would recommend to move them outside of firmware.

This is unrelated, but it can also be seen that the environment of toolchain 2.9.0 is referred but it's mixed with /Users/bruno/zephyr-sdk-0.17.0, is there any reason for this? The toolchain 2.9.0 already includes zephyr-sdk-0.17.0, this is just confusing and also leads to potential conflicting requirements for tools to be installed in PATH for no reason.

We don't suggest to use python virtual environments, that will not work under VS Code.

-Priyanka

RE: VSCode Extension Host Keeps Crashing As Soon as First Project is Added

brunohaid — Mon, 03 Feb 2025 12:35:41 GMT

Hi Priyanka, env itself should be in the support information I posted, machine is an M2 Macbook, but it happens on both Windows and Mac.

To help with usage/debugging in the meantime: see my previous questions if there's a way to tell nRF Connect to not traverse the entire monorepo? We're still getting various "west.yml found" messages, despite our application(s) already having proper build configurations pointing to the zephyr / SDK folders we want to use, which tells me that Connect is still looking everywhere across the repo.

Something along the lines of the now deprecated nrf-connect.toolchain.path or nrf-connect.topdir.

RE: VSCode Extension Host Keeps Crashing As Soon as First Project is Added

Priyanka — Mon, 03 Feb 2025 09:04:49 GMT

Hi Bruno,

I check this internally with experts and they asked whether you could share your environment setup and confirm whether you have this issue on multiple machines?

Regards,

Priyanka

RE: VSCode Extension Host Keeps Crashing As Soon as First Project is Added

brunohaid — Tue, 28 Jan 2025 14:15:34 GMT

Yes, the issue persist if nRF Connect is the only active extension.

RE: VSCode Extension Host Keeps Crashing As Soon as First Project is Added

Priyanka — Tue, 28 Jan 2025 08:28:31 GMT

Hi,

Setting the c/c++ config will not make any differance as nRF Connect for VSCode will overwrite these settings via API.
So to make sure we are on the same page:
You have Disabled the c/c++ extension and the issue persists?

-Priyanka

RE: VSCode Extension Host Keeps Crashing As Soon as First Project is Added

brunohaid — Mon, 27 Jan 2025 14:04:55 GMT

Hi & thanks Priyanka!

That was one of the first things we tried (see "What we tried so far"), problem still persist. We also tried having the extensions on, but with an empty profile:

// ---------- Nordic Semi Projects ----------

{
"name": "Nordic"
},

in our cpp config json. Neither makes any difference. Unfortunately don't know enough about the VSCode plumbing to help more with debugging, but given the good old sign "macbook gets hot", I assume the Nordic SDK extension gets hung up in some sort of circular / infinite loop.

Do you know if there's a setting with which we could tell the nRF plugin to not scour the entire workspace, but only the directory the Nordic forked Zephyr, nrf, nrfxlib is installed in?

RE: VSCode Extension Host Keeps Crashing As Soon as First Project is Added

Priyanka — Mon, 27 Jan 2025 10:20:09 GMT

Hi,

Could you try to disable the c/c++ extension and see if issue persists?

If issue is not present you can try to install older version of the c/c++ extension to see if this is a new bug introduced by Microsoft.

-Priyanka

RE: VSCode Extension Host Keeps Crashing As Soon as First Project is Added

Priyanka — Mon, 27 Jan 2025 09:27:53 GMT

Hi Bruno,

I am looking into this. I will check this internally and get back to you.

Regards,

Priyanka