TestNG MethodResult kept in memory?

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major
    • Component/s: testng-plugin
    • None
    • Environment:
      Jenkins 1.409.2, TestNG plugin 0.27

      I've just had the situation that our Jenkins instance was busy all the time with Full GCs and therefore did respond only very slowly.
      Looking at jmap -histo it showed that hudson.plugins.testng.results.MethodResult was on 3rd position. Is it possible that these results are pinned in memory? And if so, could it be refactored so they could be collected on demand - i.e. weak references?

            Assignee:
            nalin_makar
            Reporter:
            kutzi
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: