On Fri, Sep 21, 2012 at 9:02 AM, Tom Brown <[email protected]> wrote: > Hi all, > > I was having some odd server pauses that appeared to be related to my > usage of a coprocessor endpoint. To help me monitor these, I attempted > to use the task monitor; Now I've got a memory leak and I suspect it's > because I'm not correctly marking each monitored task as completed > (YourKit shows that the majority of the memory is taken up by char[]s > that contain the statuses of my tasks). > > I was unable to find good documentation about monitored tasks, so I > inferred that calling either "markComplete" or "abort" on each task > would be sufficient. Can anybody tell me the right way to clean up > these items? Is there a right way? >
You checked how other monitored tasks are done in the task monitor? markComplete seems right. Anything else referencing these tasks other than task monitor? St.Ack
