-
Bug
-
Resolution: Fixed
-
P4
-
8
tested against jdk8-fsc-b129 (don't know which version that is in the combo above ;-)
Looks like a JavaBeanProperty is never garbage collected. The snippet below (full working example and further details at SO http://stackoverflow.com/a/21579555/203657 ) creates a bunch of adapters just for local fun, they build up in memory and there's no way - at least I couldn't fine any - to get rid of them again.
@Override
public void handle(ActionEvent paramT) {
Property propertyFX;
for (int i = 0; i < 100000; i++) {
propertyFX = createCountProperty();
}
LOG.info("created 100k adapters");
}
protected JavaBeanDoubleProperty createJavaBeanProperty(){
try {
return JavaBeanDoublePropertyBuilder.create()
.bean(counter).name("count").build();
} catch (NoSuchMethodException e) {
e.printStackTrace();
}
return null;
}
This behaviour was introduced sometime during jdk8.
Looks like a JavaBeanProperty is never garbage collected. The snippet below (full working example and further details at SO http://stackoverflow.com/a/21579555/203657 ) creates a bunch of adapters just for local fun, they build up in memory and there's no way - at least I couldn't fine any - to get rid of them again.
@Override
public void handle(ActionEvent paramT) {
Property propertyFX;
for (int i = 0; i < 100000; i++) {
propertyFX = createCountProperty();
}
LOG.info("created 100k adapters");
}
protected JavaBeanDoubleProperty createJavaBeanProperty(){
try {
return JavaBeanDoublePropertyBuilder.create()
.bean(counter).name("count").build();
} catch (NoSuchMethodException e) {
e.printStackTrace();
}
return null;
}
This behaviour was introduced sometime during jdk8.
- duplicates
-
JDK-8092640 [Beans] Memory Leak in combination with JavaBeanObjectProperty
- Resolved