Performance Problems

[ronanmockett]

Recently when I navigate through my code this plugin is causing significant delays when opening a file or navigating by the "Go to definition" action. The delay seems to be in two places.

1. Finding and opening the file. (up to 2s of delay)
2. After the file has opened, all keyboard inputs are delayed for ~.5s

Upon further investigation this seems to be because my project includes a "vendors" directory with source code for opensource libraries. Using colorize.exclude and excluding the "vendors" directory resolves the issue but this seems to be a performance issue introduced with recent changes.

Using an older version of this extension like the version forked by "YuTengjing" @ version 0.12.13 the issue is not present. I am using the latest version of your extension. 0.16.0

I will provide a repository shortly for recreation.
https://github.com/ronanmockett/vscode-colorize-issue-999

Minimal extensions for reproduction
Python (Pylance, Python Debugger)
Colorize

[ronanmockett]

Potentially been mentioned before: #945

[KamiKillertO]

@ronanmockett can you share your config?
Also, the extension's default settings are JS dev-oriented, so it may be fetching more files than it should to extract variables.
By default, when opening a project the extension will search for all files that can be colorized by the extension and search for variables (CSS, SASS...) inside. This search process can take time depending on your config and consumes lots of resources.
I'm working on improving this but it's a difficult task as the extension code is old and not so well organized anymore 😅.
So right now the way to reduce the performance issue is to make sure the include, exclude, and languages configs only target the needed files.
So first, if you are using a package manager exclude the dependencies folder to prevent colorize from scanning it.

[ronanmockett]

Hi @KamiKillertO ,

I believe most of my config are just the defaults.

In my user config
"colorize.exclude": [
"/.git",
"/.svn",
"/.hg",
"/CVS",
"/.DS_Store",
"/.git",
"/node_modules",
"/bower_components",
"/tmp",
"/dist",
"/tests",
"/vendor" <-- I added this to fix my issue.
],
"colorize.languages": ["typescript", "javascript", "css", "scss"]

It does seem like this issue was introduced with the LSP refactor. It seems like more files are being included than before. Either that or the LSP stuff is blocking and the previous approach was not? 🤷

I've not worked with vscode extensions before but perhaps if I find some time I'll look into the source code :)

Many thanks, Ronan

[KamiKillertO]

The LSP should not block the UI, that's why I'm converting the extension. But maybe I've made an error on the client side.
I've also fixed an issue regarding path while introducing the LSP, so maybe that's the reason why more files are analysed now.
Does adding vendor in the settings fixed the issue for you?

[ronanmockett]

Yep, excluding vendor files fixes my issues 👍

[paradite]

Hi. I just want to report that I had this performance issue for several weeks for my Electron + Vue.js project and it was driving me crazy.

For some reason it was working fine for my old project, but not the new project I recently created.

Both projects are using the colorize plugin, new project is using tailwindcss if that matters. This caused me to believe it was something else. I went through TS and Vue language servers and found nothing suspicious. Finally I looked at the Cursor output -> Window section and noticed something strange:

2025-04-19 17:14:03.177 [warning] UNRESPONSIVE extension host: 'kamikillerto.vscode-colorize' took 85.13770435381174% of 2473.676ms, saved PROFILE here: 'file:///var/folders/ky/44xx8vp571v1z2gg7tv54wrm0000gn/T/exthost-0e0f1f.cpuprofile'
2025-04-19 17:14:50.665 [info] Extension host (LocalProcess pid: 29728) is unresponsive.
2025-04-19 17:14:50.915 [info] UNRESPONSIVE extension host: starting to profile NOW
2025-04-19 17:14:53.492 [info] Extension host (LocalProcess pid: 29728) is responsive.
2025-04-19 17:14:53.492 [info] UNRESPONSIVE extension host: received responsive event and cancelling profiling session
2025-04-19 17:14:53.746 [warning] UNRESPONSIVE extension host: 'kamikillerto.vscode-colorize' took 98.7888573324321% of 2548.958ms, saved PROFILE here: 'file:///var/folders/ky/44xx8vp571v1z2gg7tv54wrm0000gn/T/exthost-37c01d.cpuprofile'
2025-04-19 17:14:57.565 [info] Extension host (LocalProcess pid: 29728) is unresponsive.
2025-04-19 17:14:57.847 [info] UNRESPONSIVE extension host: starting to profile NOW
2025-04-19 17:15:00.094 [info] Extension host (LocalProcess pid: 29728) is responsive.

After disabling the colorize plugin, everything works again (go to definition, open link, etc).

I will wait for a potential fix before I turn it back on.

[paradite]

Here is one of the cpuprofile:

The function that is taking up a lot of time:

async function Gh(n){mc||await lx(U.serverPath);