[MASTER POST] Pigments slow, unresponding, lagging, blocking, causing Atom to lag, high activation time, insane memory usage
- Linguagem predominante
- CoffeeScript
- Estrelas
- 518
- Forks
- 70
- Métricas de merge de PRs
- Nenhum PR com merge em 30d
Descrição
This has been a long standing issue, and still is. There are multiple issues on Github regarding this problem, and most of them boil down to the same thing: Pigments is slow. We are aware of this problem, and we are sorry.
To clear things up a bit, I decided to bundle links to all issues into one master post. One issue might contain more information than another, so I've tried to sort them by amount of messages and "usefulness".
https://github.com/abe33/atom-pigments/issues/125 (38, cpu timeline, dummy file, insights)
#363 (5, script to trigger issue)
https://github.com/abe33/atom-pigments/issues/275 (22, insight: might be related to Anti-Virus)
https://github.com/abe33/atom-pigments/issues/116 (6, cpu timeline, insights)
#366 (1, only occurs on some markers)
https://github.com/abe33/atom-pigments/issues/188 (19, cpu timeline)
https://github.com/abe33/atom-pigments/issues/330 (16, commands, stack trace)
https://github.com/abe33/atom-pigments/issues/308 (14, stack trace)
https://github.com/abe33/atom-pigments/issues/175 (20, dummy project)
https://github.com/abe33/atom-pigments/issues/43 (16, dummy file)
https://github.com/abe33/atom-pigments/issues/95 (5, dummy file)
Mostly "me too", "same", +1, :+1:, confirmations:
https://github.com/abe33/atom-pigments/issues/293 (9)
https://github.com/abe33/atom-pigments/issues/121 (6)
https://github.com/abe33/atom-pigments/issues/340 (5)
https://github.com/abe33/atom-pigments/issues/306 (5)
https://github.com/abe33/atom-pigments/issues/202 (4)
https://github.com/abe33/atom-pigments/issues/235 (2)
https://github.com/abe33/atom-pigments/issues/159 (2)
#360 (1)
#367 (1)
#421 (3)
I'd like to ask you all to post any more future information here, to keep it somewhat manageable. Thanks.
## Sidenote
As some of you might have noticed, @abe33 seems to be focused on [another project](https://github.com/kiteco/atom-plugin). Because of that, maintenance on `pigments` is slowed down (update: has been brought to a stop).
In the meantime, I'm trying to keep the issues clear, the labels accurate, and to solve small issues. I don't think I'm able to solve this (major) issue on my own, that's why I'm trying to make it easier for others to help.
## General recommendations
If the latest version doesn't work, you could try downgrading pigments by uninstalling it, and reinstalling a specific version via `apm`:
```sh
apm install "pigments@0.38.0"
```
If `pigments` still doesn't work for you, [`color-picker`](https://atom.io/packages/color-picker) or [`highlight-css-color`](https://atom.io/packages/highlight-css-color) might. A (prehistoric) version of pigments, known as [`atom-color-highlight`](https://github.com/abe33/atom-color-highlight) is still downloadable too. No guarantees are given for any of them to work.
Guia de contribuição
Direção de pesquisa
This is a master issue collecting many reports of performance problems (slow, lagging, high memory). Start by reviewing the linked issues for common patterns, CPU timelines, and stack traces. Look at the project's codebase to understand how color parsing and rendering works. The goal is to identify bottlenecks, but this is a complex, long-standing issue requiring deep familiarity with the Atom plugin ecosystem and performance profiling.
Escrita pelo modelo de indexação a partir do texto da issue.
Avaliação
- Stack de tecnologia
- coffeescript
- Domínio
- devtools, tooling
- Tipo de issue
- Bug
- Dificuldade
- 5/5
- Tempo estimado
- Mais de uma semana
- Status de atividade
- Estagnada
- Clareza
- Razoavelmente clara
- Facilidade para iniciantes
- 25/100