You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The history inside fprime-gds is cleaned only when the data are sent to the GUI. If for some reason the GUI is not opened(for example when using the option -g none) the history is never cleaned. If Fprime and gds is run for enough time they will eventually take all the memory available and crash.
How to Reproduce
Start fprime-gds with the option -g none
Start an Fprime executable(it would be better if the executable publish channel with a lot of data and/or very frequently)
Let it run for a while(like half an hour) and check the memory consumption of your device.
Expected Behavior
Memory consumption should not grow without limits.
Possible fixes
A fix I thought but I'm not sure it's acceptable is to add a maximum history size in SelfCleaningRamHistory. When the history reaches the maximum size, the first element added in the history can be removed avoiding unlimited growth.
I was also thinking of disabling the history when there is no GUI but from the structure of GDS I'm not sure is possible.
The text was updated successfully, but these errors were encountered:
Problem Description
The history inside
fprime-gds
is cleaned only when the data are sent to the GUI. If for some reason the GUI is not opened(for example when using the option-g none
) the history is never cleaned. If Fprime and gds is run for enough time they will eventually take all the memory available and crash.How to Reproduce
-g none
Expected Behavior
Memory consumption should not grow without limits.
Possible fixes
A fix I thought but I'm not sure it's acceptable is to add a maximum history size in
SelfCleaningRamHistory
. When the history reaches the maximum size, the first element added in the history can be removed avoiding unlimited growth.I was also thinking of disabling the history when there is no GUI but from the structure of GDS I'm not sure is possible.
The text was updated successfully, but these errors were encountered: