> 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.

-------------

Changes:
  - all: https://git.openjdk.java.net/jfx/pull/584/files
  - new: https://git.openjdk.java.net/jfx/pull/584/files/56c2c8dc..c603d2b1

Webrevs:
 - full: https://webrevs.openjdk.java.net/?repo=jfx&pr=584&range=01
 - incr: https://webrevs.openjdk.java.net/?repo=jfx&pr=584&range=00-01

  Stats: 42 lines in 2 files changed: 31 ins; 11 del; 0 mod
  Patch: https://git.openjdk.java.net/jfx/pull/584.diff
  Fetch: git fetch https://git.openjdk.java.net/jfx pull/584/head:pull/584

PR: https://git.openjdk.java.net/jfx/pull/584

Reply via email to