-
Notifications
You must be signed in to change notification settings - Fork 141
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
power widget consumes all RAM #134
Comments
@victorz My environment is almost identical to yours, and I can't replicate this, so we'll have to dig deeper.
The difference could be in the CPU, but that would be strange. I may provide a small program to see what the power subsystem is reporting to see if there's any leads there. Thanks for the report. |
@xxxserxxx Fellow Archer! I'll try my best to answer your questions below:
I hope this helps! |
Hmm. I re-installed, this time from
I'm still not having trouble running it in
Did you ever create a This tarball has a very small program to dump out the information from the battery library. Can you run it?
and paste the results? Or let me know if it hangs? |
Thanks for getting back to this! Sorry I didn't reply sooner!
No to both -- I have no config file and I'm not running it using any command line options apart from those I listed in the issue description, so it's completely vanilla.
That program does not hang, and runs with the following output:
0 batteries seems reasonable as I have a desktop computer. (Probably not the main take-away from this output though lol) 👍 |
Hm. I don't know that I've ever run the power widget on a machine without a battery, so that's a good lead, thanks. Not sure why it would act that way, but it helps if I can reproduce it, and this may help me do that. Since you don't have a battery, the Detailed instructions are here, but in short:
|
I first tried running
gotop --layout kitchensink
but nothing is displayed in the terminal, and my RAM usage shoots to maximum usage (have to stop the process at about 28/32 GB usage due to fear of system locking...). I then triedecho '3:power' | gotop -l -
and the same thing happens.Apologies if this is already resolved. I tried searching the commit history for "power", "RAM", and "memory"-related commit messages, but couldn't find anything relevant.
gotop version: v4.0.0 (20200607T220622)
OS/Arch: GNU/Linux 5.6.15-arch1-1
Terminal emulator: gnome-terminal
Any relevant hardware info: 32 GB 3200 MHz RAM, AMD Ryzen 9 3900X 12-core
tmux version: 3.1b
~/.local/state/gotop/errors.log
: N/A -- it doesn't exist.Please let me know if you need any more information from me and I shall try to provide it for you.
The text was updated successfully, but these errors were encountered: