question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Extension causes high cpu load

See original GitHub issue
  • Issue Type: Performance
  • Extension Name: vscode-colorize
  • Extension Version: 0.8.13
  • OS Version: Darwin x64 15.6.0
  • VSCode version: 1.38.1

⚠️ Make sure to attach this file from your home-directory: ⚠️/Users/tipografia/kamikillerto.vscode-colorize-unresponsive.cpuprofile.txt

Find more details here: https://github.com/Microsoft/vscode/wiki/Explain:-extension-causes-high-cpu-load

Issue Analytics

  • State:open
  • Created 4 years ago
  • Reactions:2
  • Comments:6 (2 by maintainers)

github_iconTop GitHub Comments

7reactions
KamiKillertOcommented, Sep 18, 2019

Thanks @mahdizakizadeh for the file, I’ll have a look. I’m well aware of the performance issues, I’m working on it.

However there’s already ways to reduce/fix them. Colorize have a lots of settings with default values that target a wide range of files/languages. By changing those settings you can reduce the amount of work done by colorize everytimes you open a project or a file.

For exemple by default colorize generate background colors for every colors in the opened files, by setting colorize.colorize_only_visible_beta to true, colorize will only generate background for the visible part of the file(this setting can have huge impact when working on large files).

By default colorize generate background for SASS,LESS,CSS,STYLUS variables, but this also have some performance impact because the extension need to scan all files in a project in order to find the variables declarations. The setting colorize.colorized_variables let you define a list of variables that will be colorized. If you only use SASS change this setting to colorize.colorized_variables: ["SASS"] that way the extension will only search SASS variables.

All settings are listed here

1reaction
dmcreativestudioscommented, Sep 26, 2019

@KamiKillertO just want to say thanks for all your hard work

Read more comments on GitHub >

github_iconTop Results From Across the Web

Extension causes high cpu load · Issue #1033 - GitHub
Recently I upgraded my global eslint to v7, if that's important, but I believe the high CPU usage goes back a long way....
Read more >
[SOLVED] Chrome High CPU Usage - Driver Easy
Chrome extensions are also known to cause Chrome high system resources usage, such as 100% CPU, memory or disk usage.
Read more >
VS Code using all of the CPUs and how to fix it - Remy Sharp
TL;DR: (yes, I ramble): use "Start extension bisect" in VS Code, it'll take less than 5 minutes. This is what I'm talking about....
Read more >
High CPU usage: What are the potential causes? - IONOS
Causes of high processor usage · Programs with higher CPU requirements: · Autostart programs: · Viruses · Browser: ...
Read more >
High CPU usage due to CEPHtmlEngine - Adobe Support
Solution 1: Delete the plug-in extension folder causing high CPU usage · Solution 2: Check the log files folder · macOS · Windows...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found