abe33 / abe33/minimap-pigments
Atom crashes when minimap-pigments enabled
- Dominant language
- CoffeeScript
- Stars
- 15
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
I've been seeing my editor crash when using Atom with minimap-pigments enabled; I'm seeing 110+% of my CPU being used. This has been occurring since I updated to v1.13 and persists on v1.14 of Atom.
I am not entirely sure if the issue is with this package or pigments in general, though my suspicion is that it deals with this package.
I do see high CPU usage with pigments, and some slow down of typing, but it is more sporadic. I see dramatically high CPU usage and crashes every time minimap-pigments is enabled.
**OS:** 10.12 Sierra
**Atom Version:** 1.14.1
**Package Version:** 0.2.2
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue describes a crash and high CPU usage when minimap-pigments is enabled in Atom. Start by reproducing the crash with Atom v1.14.1 and the package version 0.2.2 on macOS Sierra. Look at the package's main CoffeeScript files and the interaction with the pigments package. Check for infinite loops or heavy processing in the minimap rendering. Profiling CPU usage in Atom's developer tools may help identify the bottleneck.
Written by the indexing model from the issue text.
Assessment
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100