-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Computer gets unresponsive after running Realtime Plotter for a long time #1446
Labels
Milestone
Comments
flixr
added a commit
to flixr/paparazzi
that referenced
this issue
Nov 29, 2015
first of all the image/label with the current value is not displayed anymore (at least on Ubuntu 14.04). And probably more importantly, these constant updates of the menu result in high cpu-load and memory usage of hud-service, rendering the computer unusable if left running for a long time (until hud-service is killed and restarted). Workaround for paparazzi#1446 by simply disabling the update of these labels/menu entries
Btw, this seems to be Unitiy specific issue (since |
flixr
added a commit
to flixr/paparazzi
that referenced
this issue
Nov 30, 2015
first of all the image/label with the current value is not displayed anymore (at least on Ubuntu 14.04). And probably more importantly, these constant updates of the menu result in high cpu-load and memory usage of hud-service, rendering the computer unusable if left running for a long time (until hud-service is killed and restarted). Workaround for paparazzi#1446 by simply disabling the update of these labels/menu entries
Closing, since workaround of disabling the menu updates (as per #1447) works for now.... |
fvantienen
pushed a commit
to fvantienen/paparazzi
that referenced
this issue
Oct 6, 2016
See paparazzi#1445 updates were disabled already due to paparazzi#1446 and not displayed on recent systems paparazzi#1445
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
From @esden on Ubuntu 14.04:
Computer gets unresponsive when running e.g. the "Raw Sensors" session with 4 realtime plotters for a long time.
The
hud-service
process seems to take up quite a bit of CPU and fills the memory until it gets unresponsive.This seems to be related to #1445: The HUD service seems to connect to menu events of all apps, and every event changing the avg/stdev values in the curves menu trigger it...
The text was updated successfully, but these errors were encountered: