yes thanks too for the description although
I feel a little more helpless now ;-)
I didn't run the Applications long enough
to tell if it crashes or not. Once I ran some in parallel (different versions
but since it was my normal working machine
and it started to swap memory it wasn't usable in that state. So I had
Another one (custom build v3.2.15, OpenJDK
7) is running for a week now and linux-top shows the following:
KiB Mem: 8125900 total, 7843444
used, 282456 free, 18452 buffers
KiB Swap: 2103292 total, 1623244
used, 480048 free, 768356 cached
PID USER PR
NI VIRT RES SHR S %CPU %MEM TIME+
20 0 6211m 3,5g 11m S 8,6
45,6 1307:53 java
Scenario is still the same (start the
program, add ca. 20 PVs updating its values at 4Hz).
Maybe this one will grab the "rest"
of the free memory until Monday and we will see what happens then.
Hopefully the linux oom-killer does
Filling Memory when observing PVs
Thanks to Gabriele for the good description of general GC behavior.
With either OpenJDK or the Oracle JDK, have you seen it crash with OutOfMemoryError?
Or is it simply using memory towards the permitted limit?
I am aware of a perm gen memory issue with Jython (https://github.com/ControlSystemStudio/cs-studio/issues/256,
The CSS ticket is about the Scan Server, but it may be the same for Jython
scripts inside BOY.
The manifestation would be a pretty obvious java.lang.OutOfMemoryError: