Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8159860

JavaFX Path drawing appears to leak native memory

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: P3
    • Resolution: Fixed
    • Affects Version/s: 8u92, 9
    • Fix Version/s: 9
    • Component/s: javafx
    • Labels:
      None
    • Environment:

      Windows 10.0
      OS X 10.11.5
      Java 8u92

    • Subcomponent:
    • CPU:
      x86
    • OS:
      os_x, windows_10

      Backports

        Description

        Repeated drawing of Paths appears to slowly leak native memory. A project is attached that can be run with gradle.

        The test code paints 100 paths repeatedly. While it is running, observe the process memory usage with a tool like Process Explorer or Task Manager on Windows, or Activity Monitor on OS X.

        To be sure there is a real native leak, limit the Java heap and allow the program to run for 30 minutes or so, recording the processes totally memory usage every 5 minutes. Memory fluctuations early on can make it difficult to see that the memory usage of the process steadily climbs.
        Using a tool like jvisualvm you can see that Java heap is not leaking.

        The leak is present with -Dprism.order=sw as well as using the GPU accelerated pipeline.

        Using jvisualvm to trigger GC has no effect on the native memory usage. (My thinking is that a finalizer might be used to reclaim native resources.)

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                flar Jim Graham
                Reporter:
                swpalmer Scott Palmer
                Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved: