jonathan.giles at oracle.com
Sat Oct 20 14:16:00 PDT 2012
David Grieve is the go-to expert on all things CSS, but from a
higher-level perspective the general answer is always: you tell us! :-)
There might be a leak we don't know about, or can't easily reproduce,
and you might have just the information we need to finally get rid of
that annoying leak you mention.
So, please, file Jira bugs on us and we'll get to looking at them as
soon as possible. If you can provide a reproducible test case that would
be hugely appreciated too.
Finally, from our point of view JavaFX 2.2.3 is rather old code - we've
been actively developing in the 8.0 branch for quite a long time now,
and one of our primary focuses during this time has been performance
(CPU and memory). In other words, there is a chance it may already be
resolved (or minimised) in the 8.0 branch. I know it is a lot to ask,
but there are 8.0 builds available that you can test with. If you have
the time and inclination, it might be worth testing against these builds
to see if it is resolved.
On 21/10/2012 2:10 a.m., Scott Palmer wrote:
> Are there known leaks in 2.2.3 with regards to CSS and style cache stuff?
> In my application I add and remove style classes to highlight objects in the scene graph that are in various states (selected, active, disabled, etc). It seems that every time the style class list is changed that there is a small leak. Since while the app runs and process data (a process that may run indefinitely) the state of objects in the graph changes as data is processed, this is a significant issue. Our customers may have the app fail after several hours or a few days because of these leaks.
More information about the openjfx-dev