Auto Close Tag is the culprit behind performance issues with this extension

[redtopia]

For years now I have had problems with this extension that requires a restart of vscode to fix. I do this multiple times per day, every single day. Sometimes things work great for a couple hours, sometimes only 10 minutes, but this is a consistent problem that plagues my CFML development.

When things aren't working well, I can no longer auto-close tags, I lose cfml docs when I hover over a function, I lose the ability to trigger snippets when I start typing, and sometimes things get so bad that when I rename, delete, or add a file, vscode takes a solid minute or two to perform the operation. Overall, the performance of vscode gets so poor that I have no choice but to restart.

Because restarting vscode is quick and fairly painless, I have not invested a lot of time into figuring out what is going on until recently. Editors parse as you type and since I have some large files that I'm dealing with, I just assumed that this is par for the course. However, recently I was updating a large .html file with simple HTML markup and noticed a very annoying lag that happened when I was typing my changes. I figured there's no way the vscode developers, or the community as a whole would find the lag acceptable, which tempted me to try and figure out what the heck was going on.

I restarted vscode with all extensions disabled (except the built in ones), which eliminated the lag while typing. After turning extensions on one by one, I found out that Auto Close Tag was the culprit.

So if you are having vscode performance issues with cfml and you are using the Auto Close Tag, try disabling it and see if your issues go away. Of course you lose the ability to auto close your tags, but to tell you the truth, I fix incorrectly closed tags so often that I think for me it actually saves time to not auto-close them.