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

Hight use CPU #87

Open
rtsantanna opened this issue Jan 15, 2022 · 3 comments
Open

Hight use CPU #87

rtsantanna opened this issue Jan 15, 2022 · 3 comments
Labels

Comments

@rtsantanna
Copy link

Good morning.
The application some times, use 100% of CPU:

100% 0.1 2.83G 41.4M 1525 rtsantann 1:56 12 0 R 0 0 gjs extensions/[email protected]

After kill the process, is necessary open the application, and restart daemon.

Can you send me the command / string for restart by cli ?

@flarre
Copy link

flarre commented May 14, 2022

Hello,
since last update (I waited to use desk-changer on new gnome-shell) I have the same problem here, desk changer runs for hours without problem and gjs process suddenly takes 100% CPU.
kill gjs and restart desk-changer and it's OK.
Don't know if it's related or if I have to open another thread, but there are some weird glitches in the GUI too, it's impossible to change the profiles (new delete or modify the files and folders) when main window is open.
For example if I want to make a new profile, I cannot input the name or click "ok" or "cancel" if main desk-changer parameters window is open, I must close it first, then input name and ok. The profile is created.
In order to create a profile and add folders, I must open and close multiple times the parameters.

@BigE
Copy link
Owner

BigE commented Oct 24, 2022

I've seen this happen myself, but it's very random and I don't have a cause for it yet. I would recommend enabling debugging with gsettings --schemadir ~/.local/share/gnome-shell/extensions/[email protected]/schemas set org.gnome.Shell.Extensions.DeskChanger debug true and running the daemon from a terminal with gjs ~/.local/share/gnome-shell/extensions/[email protected]/daemon/server.js You might have to stop the daemon from the extension preferences before it'll run in the terminal. Hopefully with debugging enabled, we can get something to show up that I can track down. Thanks!

@BigE BigE added the bug label Oct 24, 2022
@arthurzenika
Copy link

Getting the same bug. Here.

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

No branches or pull requests

4 participants