Skip to content
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

Very high CPU usage #32

Open
T-vK opened this issue Nov 29, 2019 · 6 comments
Open

Very high CPU usage #32

T-vK opened this issue Nov 29, 2019 · 6 comments

Comments

@T-vK
Copy link

T-vK commented Nov 29, 2019

If you take a look at the htop in this screenshot, you can see that my CPU is going completely crazy:
image
It seems like tmux, mplayer and ccze are responsible.

OS: Ubuntu 18.04
hollywood version: 1.20

I think I had the same problem with 1.19.

@T-vK
Copy link
Author

T-vK commented Dec 9, 2019

@dustinkirkland I think it would be a good idea to add a parameter to hollywood that would allow you to specify which apps hollywood should use. Maybe a blacklist, whitelist or both.
This would make debugging an issue like that much easier.
What do you think?

@dustinkirkland
Copy link
Owner

The code is trying to run hollywood with the lowest CPU priority, using the nice command. Whenever you see this behavior, could you please paste the output of this command:

$ ps -e -o uid,pid,ppid,pri,ni,cmd | grep hollywood

I'd like to ensure that the nice value of every script is 19 (the lowest priority).

@dustinkirkland
Copy link
Owner

I'm open to a patch that blacklists individual applets, but this isn't very high priority for me. Note that you can run hollywood -s SPLITS and use a smaller number of splits from the default (which is all available). Generally speaking, hollywood is going to consume a lot of CPU. That's kind of the point. It's intended to be a tongue-in-cheek joke.

@dominic-03
Copy link

I had this problem even after the program was closed. My CPU usage was constantly at 100% and my computer was running very hot. I had to kill the ccze process to get it back to normal.

@Frambooisier
Copy link

@dominic-03 same here

@yeeterlol
Copy link

same here, eated up all my cores up to 90%

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants