JPPF Issue Tracker
star_faded.png
Please log in to bookmark issues
bug_report_small.png
CLOSED  Bug report JPPF-51  -  Leak in the node: task timeout timer thread groups
Posted Aug 26, 2012 - updated Aug 26, 2012
icon_info.png This issue has been closed with status "Closed" and resolution "RESOLVED".
Issue details
  • Type of issue
    Bug report
  • Status
     
    Closed
  • Assigned to
    Not assigned to anyone
  • Progress
       
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
  • Posted by
     lolo4j
  • Owned by
    Not owned by anyone
  • Estimated time
    Not estimated
  • Category
    Node
  • Resolution
    RESOLVED
  • Priority
    High
  • Reproducability
    Always
  • Severity
    Normal
  • Targetted for
    icon_milestones.png JPPF 3.1.2
Issue description
I did a load test:
  • 1 driver, 1 node all on the same machine
  • client runs matrix multiplication demo, with matrix size = 300*300, for 500,000 iterations (150 million tasks total)
Test took about 5h30mn on my machine. After the test was ended, I used VisualVM to do a GC and take a heap dump. Heap dump analysis shows there are over 500,000 thread groups named "Task Timeout Timer thread group" that were not garbage collected, ocuupying around 100 MB of unfreeable memory
Steps to reproduce this issue
  • start 1 driver, 1 node all on the same machine
  • run the matrix multiplication demo, with matrix size = 300*300, for 500,000 iterations (150 million tasks total)
  • after the test is done, take a heap dump for the node's JVM ==> leak of task timeout timer thread groups



#2
Comment posted by
 lolo4j
Aug 26, 10:50
A file was uploaded. lek susspects report in the nodeicon_open_new.png This comment was attached:

Attched leak suspects report (generated with Eclipse MAT, a standalone heap dump analyzer). Heap dump can be downloaded from here
#3
Comment posted by
 lolo4j
Aug 26, 10:52
Fixed. Changes committed to SVN:

The issue was updated with the following change(s):
  • This issue has been closed
  • The status has been updated, from New to Closed.
  • This issue's progression has been updated to 100 percent completed.
  • The resolution has been updated, from Not determined to RESOLVED.