Not sure this is the right forum to ask but i'll try it as I don't know where else to ask. For those using VSCode to develope CF code in, have any of you recently encountered a problem where your VSC suddenly bogs down doing ? but it changes the SVN extention icon to clock icon overlay meaning it's busy. Cntrl-/ key combo to comment code doesn't work. Renaming files takes a loooong time, etc. VSC won't exit this slow down degradation till I quit and restart the app. I have reduced the extension set down to just the minimal set: CFML, Live Sass Compiler, SVN, Auto Close Tag. My laptop cooling fan runs moderately high during this time so something is going on. Any suggestions/clues would be welcomed. This issue is really impacting my productivity. This is a recent change in behavior, over the past week or two only. Before that, these and many other extensions ran fine. I don't know if it is an extension but based on the Resource Monitor, it is Code.exe that is the only process taking up CPU.

Could be a bug in the SVN support that surfaced in a recent update, perhaps? Any changes at all in your environment outside VS Code? File system mounts? Networks? Malware/security checking software?

I have had similar issues when there is a network issue connecting to SVN repos

(a big reason why git is so much better than svn!)

probably the smallest reason... Git is superior in so many ways, branching, merging, etc

Hahaha... ok, one of many reasons! 🙂

I would love to use git but the projects I'm on all use SVN. 😞 I am currently suspecting the LESS Live Compiler which has been recently updated. I disable it and it seems to keep the problem from surfacing. But I need it to live compile my SASS. It has worked flawlessly till this event. I'm not positive it is the culprit but leaning that way.

(sheesh... sccs is 50 years old, rcs is 40 years old... svn is "only" 20 years old!)

Yeah, I started out with Visual Source safe

@teaman VS Code allows you to install earlier versions of an extension so you could try the older version and see if that behaves better.

Good idea @seancorfield

Disabling it should be sufficient. I suspect SVN and network issues as Scott also suspected.

I am basically down to that one as well. Given it is code changes that triggers it, I think the SVN is getting "gummed up" with trying to compare them with repo to display changes in VSC sidebar. I note that SVN (Chris Johnston) extension was last updated June 22 2023. Not sure if the problem is in the extension or in SVN. Thanks for all your suggestions!