Replies: 3 comments 2 replies
-
|
Thats how Java works. It will allocate up to a point, and then run a garbage collection. It will keep doing this forever, because objects will be allocated. |
Beta Was this translation helpful? Give feedback.
-
|
If I'm reading that right, it's allocating 125 megabytes in 5 seconds. That certainly seems excessive. Does this occur on an empty project, or only with your full code? There are some tips for reducing memory usage here: https://docs.wpilib.org/en/latest/docs/software/basic-programming/java-gc.html |
Beta Was this translation helpful? Give feedback.
-
|
Also, free memory is going to fluctuate due to OS caching (free memory is wasted memory). Available memory is a better metric. |
Beta Was this translation helpful? Give feedback.
-
|
This occurs on a very simple robot with only drive motors. It occurs in Disabled and Enable Modes. 125 megs seems very excessive to me. How do you access available memory? |
Beta Was this translation helpful? Give feedback.
-
|
Both free and available are in top and /proc/meminfo How did you access free memory? |
Beta Was this translation helpful? Give feedback.
-
I plotted free memory on the Shuffle Board and it changes a lot even when the robot is disabled. See attached plot.
Beta Was this translation helpful? Give feedback.
All reactions