Memory leak with multiple "nodes" in CustomNode

Question

The displayed GUI has the ability to update a view when u press a button.
If I press this button many times the process becomes longer and finally results in " java.lang.OutOfMemoryError: Java heap space "
I think the problem is created by the update function when I remove the customnode from my gui and replace it by another...
The custom node (main part)
Bars containing:
for(h in [0..days]){
insert line[h] = Line {
startX: beginBalk + 5 + balkBreedte * h,
startY: 0
endX: beginBalk + 5 + balkBreedte * h
endY: 30
strokeWidth: 1
stroke: Color.BROWN
} into grp.content
This group is returned and added to another customnode (BarViewer) which is displayed.
When I update the bar im using:
BarViewer code:
delete bar from grp.content;
insert bar = Bar{
translateY: 10
} into grp.content
Hope someone knows the (simple?) answer ;-)

Answer 1

Thx for the reply Phil_ho,
I created a new project and filled it with a function that creates CustomNodes filled with lines and other javafx components and used profiling & telemetry to analyse... No problems found.
I went back to my original design and found the problem in the following code:
insert textField = SwingTextField {
columns: 20
borderless: false;
width: beginBalk - 5;
height: 30;
enabled:false;
text: "";//hist.getToelichting();
editable: false;
} into grp.content;
If I replace the code above with a javafx text component (or any other component for that matter) the Garbage Collector kicks in.
Apparently swing components are harder to release by the GC or something. Still havent figured out how to implement them with the proper GC support so perhaps u could shine a light on this issue ;-)
Edited by: Hugo_Groeneveld on Mar 29, 2009 3:59 AM