Connor Peet

Results 461 comments of Connor Peet

That's right. But specifically, I usually have the vscode-copilot repo open which has its long running watch tasks, so that may also be a part of it.

I updated Insiders today without a debugging session and didn't run into the issue 🙂

This broke my Insiders build today, I think I tried to cancel setup when the issue happened and then I opened Insiders again to see if that would work without...

Today and for the mid-day Insiders yesterday I was much more careful about the update > just to validate this scenario can you check if update fails when you don't...

Unfortunately I got this updating Friday -> Today's Insiders ![image](https://github.com/user-attachments/assets/6ae8f5f9-11e4-42f8-87e7-e006a61db862)

Will do next time I hit this

I don't see much of a tree in Process Exporer, but here's some info: ![image](https://github.com/user-attachments/assets/c4100c07-9285-4826-b6da-d6bccc7aaa09) ![image](https://github.com/user-attachments/assets/30ce6223-0711-419b-ab77-3de217c6e7b6) I also took a minidump of the process if that would be helpful

I still see some leak on the latest preview `0.55.0-dev-20251105` , using the codesandbox example linked above after 2000 iterations:

Please update your VS Code version to get the fix.