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.

Sign up for GitHub

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

Jump to bottom

Latest master make machine runs heavy. #71

Closed
ahmadraniri1994 opened this issue Oct 15, 2021 · 11 comments
Closed

Latest master make machine runs heavy. #71

ahmadraniri1994 opened this issue Oct 15, 2021 · 11 comments

Comments

@ahmadraniri1994
Copy link

I'm sorry for non-technical description, I compile latest master and run it, something I notice is my fan runs faster. It doesn't happen when I use other Wayland compositor (e.g Sway, hikari) and Labwc from my previous compilation (before the latest master). Happening for both archlinux and Debian. Thanks.
@johanmalm
Copy link
Collaborator

Thanks for feedback.
I know it’s a big ask, but it there any chance you could establish what commit (in labwc or wlroots) had this effect?

If you run ‘top’ from a terminal you can monitor CPU usage.

Are you running swaybg or similar? Does that have an effect on CPU usage?

@ahmadraniri1994
Copy link
Author

I'm running swaybg and turns out when I disable swaybg from autostart, The CPU's usage becomes lower and my fan becomes normal. Thanks, it works.

@ahmadraniri1994
Copy link
Author

Perhaps I need to close this issue.

@01micko
Copy link
Contributor

01micko commented Oct 15, 2021

I've also noted that swaybg consumes much cpu.

Screeny from lxtask

swaybg

@johanmalm
Copy link
Collaborator

We’ll need to establish why. Could be swaybg, wlroots or labwc.

swaybg never used to be CPU heavy on labwc, so something has changed.

Grateful for any detective work you can. Otherwise I’ll investigate tonight.

@johanmalm
Copy link
Collaborator

I've also noted that swaybg consumes much cpu.

Screeny from lxtask

swaybg

Is that labwc running from openbox on puppy, or labwc from tty?

@ghost
Copy link

ghost commented Oct 15, 2021

Updating swaybg to the latest github version solved this for me. I believe that swaywm/swaybg@5e2df3a is the reason why.

johanmalm added a commit that referenced this issue Oct 15, 2021
@johanmalm
layer-shell: fix commit handler (issue #71)
73b8f06 
On commit, do not arrange layers unless the layer shell-specific state
changed or the layer was (un)mapped.

Chase swaywm/sway@5fd5d643 and swaywm/wlroots@754f40f9
@johanmalm
Copy link
Collaborator

@ARDiDo - like passing ships. That's interesting!
I've pushed a fix that sorts it for the old version too.
It works on mine, so will close this issue for now. Shout if it persists for anyone.

@01micko
Copy link
Contributor

01micko commented Oct 15, 2021

Is that labwc running from openbox on puppy, or labwc from tty?

tty, pure wayland. I've been experimenting in Puppy. See puppylinux-woof-CE/woof-CE#2563

I intend updating everything to latest version this weekend.

@01micko
Copy link
Contributor

01micko commented Oct 15, 2021

Excellent! Thank you 😃

20211016_06h08m53s_grim

@johanmalm
Copy link
Collaborator

Is that labwc running from openbox on puppy, or labwc from tty?

tty, pure wayland. I've been experimenting in Puppy. See puppylinux-woof-CE/woof-CE#2563

I intend updating everything to latest version this weekend.

Great stuff.
You've got some good wall-paper scripts there. Will give them a go.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@01micko @johanmalm @ahmadraniri1994