You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
go tool pprof cpu.profile after you close out the profiling build of gh-dash will open up the interactive tool google ship for probing the profile.
The top10 command might shed some light on what is actually using CPU cycles, or the web command should generate a nice visualisation of where they're all going in your browser.
Describe the bug
A clear and concise description of what the bug is.
Just running the extension consumes about a quarter of the CPU resources. This behaviour is unexpected
To Reproduce
Steps to reproduce the behavior:
Activity Monitor app
Activity Monitor
app and check forgh dash
process nameExpected behavior
A clear and concise description of what you expected to happen.
Consume less cpu %. For example running
kitty
instance consumes just about0.6%
of cpu. actively runningeslint_d
instance consumes not more than15%
.Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Update:
Used extension ver.: 4.3.0
The text was updated successfully, but these errors were encountered: