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

File descriptor leak within WinAppBundler

XMLWordPrintable

    • x86
    • windows_8

      FULL PRODUCT VERSION :
      java version "1.8.0_72"
      Java(TM) SE Runtime Environment (build 1.8.0_72-b15)
      Java HotSpot(TM) 64-Bit Server VM (build 25.72-b15, mixed mode)

      ADDITIONAL OS VERSION INFORMATION :
      Microsoft Windows [Version 6.3.9600]

      A DESCRIPTION OF THE PROBLEM :
      I'm the developer and maintainer of the javafx-gradle-plugin.

      While creating support for the daemon-mode of gradle, some user reported that the clean-task wasn't successful. After some deeper research I found out, that there is a file handle open to the bin-folder inside the copied RUNTIME.

      When copying the microsoft runtime DLLs, the stream returned by Files.list() isn't closed resulting to a still open file handle. That file handle stays open, because the JVM is not stopped and the handle isn't closed.

      I have searched for that problem and I might have found it here:
      http://hg.openjdk.java.net/openjfx/8u60/rt/file/996511a322b7/modules/fxpackager/src/main/java/com/oracle/tools/packager/windows/WinAppBundler.java#l325

      Some more details found at the isse:
      https://github.com/FibreFoX/javafx-gradle-plugin/issues/12#issuecomment-176443925

      "As this stream is a DirectoryStream (as documented), this should have to be closed, mostly by using try(resouce){}-syntax."

      EXPECTED VERSUS ACTUAL BEHAVIOR :
      EXPECTED -
      No file handle on the runtime/bin-folder

      REPRODUCIBILITY :
      This bug can be reproduced always.

            cbensen Chris Bensen (Inactive)
            webbuggrp Webbug Group
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: