Closed nguxx closed 2 years ago
pfps
commented
2 years ago Please run Solaar from your clone of the GitHub respository as bin/solaar -dd. When Solaar is consuming too much CPU interrupt it with control-C and post the output including the backtrace from the interrupt.
nguxx
commented
2 years ago Hi, Sorry too be so late, very buzzy AFK. So this what I reproduce (htop give me up to 90 but ps stay under 80, still high no ?):
bash
:~/Solaar$ ps u -C python3
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
ngux 4860 79.5 0.1 793524 72044 pts/0 Sl+ 02:40 1:56 python3 /home/nguxBut I have to say that the git clone version works better than the one I got on apt which was higher (reaching 100 most of the time). Usually, the git clone version is around 25% of CPU. Even 25 seems high, what do you think?
debug
After the ^C
I got the 500 last lines, enough ?
(next code block I relauch a processus for you to see the begin of the debug):
Another processus from the begining:
pfps
commented
2 years ago Does Solaar start consuming CPU immediately? Does this state continue indefinitely? Does the Solaar main window eventually show up and can you then change device settings?
It looks as if the debugging output you provided come very shortly after Solaar starts.
nguxx
commented
2 years ago Does Solaar start consuming CPU immediately?
Not aways. For now I didn't succeed to understand what is the trigger...
Does this state continue indefinitely?
When it starts to go up, it doesn't stop. Usually that the restless activity of the fan which warn me.
Does the Solaar main window eventually show up and can you then change device settings?
The window does not pop up but i can open it and I can change device settings.
I can say that the git version usually use 20% of CPU and works better than the apt repository version. Yesterday I hit 100% but I forgot to save the debug before killing the processes. I now always open solaar with -dd so, I'll give you another debug next time it goes awry.
pfps
commented
2 years ago OK. I'll wait for the next run.
By the way, please use -ddd to get even more debug information.
pfps
commented
2 years ago Seems to be the same as #1455
pfps
commented
2 years ago @nguxx Please try the testing suggested in issue #1455
pfps
commented
2 years ago @nguxx Have you had a chance to test the PR?
nguxx
commented
2 years ago Hi pfps, In deed I have plenty of no-op operation and in deed I have a K380 keyboard. Because I'm not enough familiar with git I'm not sure to have done the right thing I run the commands :
git fetch origin pull/1456/head:pull_1456
git checkout pull_1456then
git checkout pull_1456
git fetch origin pull/1456/head
git reset --hard FETCH_HEADand eventually I run
$HOME/Solaar/bin/solaar
The amount of CPU is better than before but still around 10 and 15%
Did I get it right ?
pfps
commented
2 years ago You didn't have to do both of these, but there was no harm in doing the second group.
10-15% CPU utilization seems rather high, but if Solaar is behaving normally, i.e., you can make whatever changes you need to make, then I guess that is what you can expect. But let me see if detecting these no-ops earlier cuts down on the CPU utilization.
pfps
commented
2 years ago Try PR #1474. It detects no-op notifications even earlier.
In the Solaar directory:
git fetch origin pull/1474/head:pull_1474
git checkout pull_1474Then kill Solaar and run bin/solaar. See how much CPU it uses when the keyboard is active.
nguxx
commented
2 years ago Try PR #1474. It detects no-op notifications even earlier.
In the Solaar directory:
git fetch origin pull/1474/head:pull_1474 git checkout pull_1474Then kill Solaar and run
bin/solaar. See how much CPU it uses when the keyboard is active.
This is perfect! take a look at this
$ ps u -C python3
PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
10211 0.9 0.1 719488 72372 pts/3 Sl+ 11:14 0:01 python3 bin/solaareven if I use intensively the keyboard it never reaches more than 2% for 1 sec and goes back less than 1%. Everything in the windows is functional (connection a K380 and a mouse M590) Thanks a lot for your work ! :100:
Information
solaar --versionorgit describe --tagsif cloned from this repository):solaar 1.1.1and1.1.1-80-gf938d34uname -srmo):Linux 5.15.0-2-amd64 x86_64 GNU/Linuxsolaar show:Describe the bug solaar take almost 100% of one logical CPU.
Tried :
sudo apt install solaar: same issueNote The
solaar showis from the last install from git Thanks