RFR: 8269907 memory leak - Dirty Nodes / Parent removed [v2]
Kevin Rushforth
kcr at openjdk.java.net
Thu Jul 22 12:42:47 UTC 2021
On Thu, 22 Jul 2021 11:50:11 GMT, Florian Kirmaier <fkirmaier at openjdk.org> wrote:
>> After thinking about this issue for some time, I've now got a solution.
>> I know put the scene in the state it is, before is was shown, when the dirtyNodes are unset, the whole scene is basically considered dirty.
>> This has the drawback of rerendering, whenever a window is "reshown", but it restores sanity about memory behaviour, which should be considered more important.
>
> Florian Kirmaier has updated the pull request incrementally with one additional commit since the last revision:
>
> JDK-8269907
> The bug is now fixed in a new way. Toolkit now supports registering CleanupListeners, which can clean up the dirty nodes, avoiding memoryleaks.
The revised approach doesn't appear to have the same threading issues that the first attempt did (good). I would have thought you could add some logic to the existing scene pulse listener instead of creating a new one. I'll take a closer look when I review this.
-------------
PR: https://git.openjdk.java.net/jfx/pull/584
More information about the openjfx-dev
mailing list