-
Notifications
You must be signed in to change notification settings - Fork 193
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
yarpmotorgui using 80% of the CPU #2955
Comments
Where you doing something particular with the |
It was just open. |
If you are able to reproduce on a physical Linux/Intel machine (no virtualization or WSL2), it may be worth to collect some trace, for example via magic-trace ( https://github.com/janestreet/magic-trace), it should be sufficient to run:
and upload (or inspect yourself) the resulting |
I will do it tomorrow, it was happening on a plain Linux machine. |
Note that I always used magic-trace attach-pid, but |
Hello, I can reproduce this on YARP version 3.8.0+3-20230306.4+git282a223a7 and Ubuntu 20.04. Here is my trace: trace.zip. I used the
There is a window prompt that shows up right after launching yarpmotorgui that allows me to select which parts I want to control. CPU usage is negligible in this step, but it rockets up to 100% once the main window is opened. Edit: I can test this app's behavior both on the Gazebo simulator and on a fake implementation of the real robot (which just returns |
I checked the CPU usage on the latest commits in the src/yarpmotorgui/ tree. It looks like 54c1a6f is the culprit (more precisely, the additions in sliderWithTarget.cpp). Also, a segfault is produced on exit. |
Describe the bug
Today I noticed that the laptop fan was spinning quite a lot and the only substantial executable running was the
yarpmotorgui
.From the screen it seems that the
yarpmotorgui
is using almost 90% of the CPU.To Reproduce
Open the
yarpmotorgui
and wait a bit.Expected behavior
That the
yarpmotorgui
do not consume that amount of CPU.Screenshots
See above.
Configuration
cc @randaz81 @traversaro
The text was updated successfully, but these errors were encountered: