Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-22088

Disk space leak with multiple copies of winstone-XXXX.jar in TEMP folder

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • core
    • Windows 8.1 x64, JDK 1.7.0_51, Jenkins 1.553

      Continued operation of Jenkins creates multiple copies of "winstone.jar" with a numeric suffix in TEMP folder (winstone12343543634634.jar). We had about 800Gb of these accumulated, slowing down the host system.

      We are currently running Jenkins directly (`java -jar jenkins.jar`) via Windows scheduled task.

          [JENKINS-22088] Disk space leak with multiple copies of winstone-XXXX.jar in TEMP folder

          Anton Tayanovskyy created issue -
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 154167 ] New: JNJira + In-Review [ 178712 ]
          Ivan Fernandez Calvo made changes -
          Assignee New: Ivan Fernandez Calvo [ ifernandezcalvo ]
          Ivan Fernandez Calvo made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]
          Ivan Fernandez Calvo made changes -
          Status Original: In Progress [ 3 ] New: In Review [ 10005 ]
          Jesse Glick made changes -
          Remote Link New: This issue links to "extras-executable-war PR 12 (Web Link)" [ 17818 ]
          Jesse Glick made changes -
          Component/s New: core [ 15593 ]
          Component/s Original: build-environment-plugin [ 17667 ]
          Jesse Glick made changes -
          Labels Original: jenkins winstone New: winstone
          James Dumay made changes -
          Remote Link New: This issue links to "CloudBees Internal OSS-2489 (Web Link)" [ 18276 ]
          Ivan Fernandez Calvo made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: In Review [ 10005 ] New: Resolved [ 5 ]
          Ivan Fernandez Calvo made changes -
          Comment [ ~if you only upgrade the Jenkins instance, the issue would be not resolved. The change is in the windows service that launches the Agent, so to resolve the issue you have to uninstall and install again the windows service if not, you would not change anything~ ]

            ifernandezcalvo Ivan Fernandez Calvo
            t0yv0 Anton Tayanovskyy
            Votes:
            20 Vote for this issue
            Watchers:
            34 Start watching this issue

              Created:
              Updated:
              Resolved: