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

Plugin consumes too much memory

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Critical Critical
    • jacoco-plugin
    • None

      Imported from GitHub: https://github.com/jenkinsci/jacoco-plugin/issues/12

      Report by Greg Temchenko ("soid" on GitHub)

      I broke down my Jenkins trying to use this plugin. It turned out that plugin stores the entire coverage in XML format in build.xml file in jenkins (JENKINS_HOME/jobs/[Project]/builds/[Build]/build.xml). Boolean values about covered/uncovered lines stored there as XML tags with indentation for readability

      <boolean>true</boolean>

      Thus my 600K code coverage .exec bin file consumed more than 700M on the hard disk for the build.xml.

      This is a half of the problem. Further Jenkins keeps all builds information including mentioned above build.xml in RAM. That's how I've caught OutOfMemory exceptions in Jenkins and got it broken.

      And a comment from Jesse Glick ("jglick")

      For what it’s worth Kohsuke & I recently did some minor memory usage fixes in the Cobertura plugin, and I experimented with more: https://github.com/jenkinsci/cobertura-plugin/compare/master...trove

      This issue makes the plugin forbidden to installation on JBoss Jenkins instance.

            ognjenb Ognjen Bubalo
            mickael_istria Mickael Istria
            Votes:
            7 Vote for this issue
            Watchers:
            12 Start watching this issue

              Created:
              Updated: