|
Re: PeriodicallyUpdateEPackageRegistryMonitorJob eats away heap [message #923099 is a reply to message #922991] |
Tue, 25 September 2012 15:46 |
|
Apparently, that class is started as soon as you launch Epsilon and it doesn't really depend on having the Concordance nature set or not. It's using the org.eclipse.ui.startup extension point, and is scheduled to poll the EPackage registry every second.
This looks like a memory leak, but it's not quite clear where it is happening. Could you provide heap dumps for the basic memory usage and the bumps right before GC kicks in? That would be quite useful.
I would also suggest querying the EPackage registry less often. I don't think we need to query it every second. Shouldn't 2 or 5 seconds be enough?
|
|
|
|
|
|
|
|
|
Re: PeriodicallyUpdateEPackageRegistryMonitorJob eats away heap [message #924108 is a reply to message #923961] |
Wed, 26 September 2012 14:13 |
Maarten Bezemer Messages: 117 Registered: February 2012 |
Senior Member |
|
|
Ed Willink wrote on Wed, 26 September 2012 12:47As I suggested, I think the leak is in the communications infrastructure.
Perhaps the server thread by which VisualVM communicates is continually
allocating new packet buffers, which are available for GC when the GC
kicks in.
This might be the case, but I noticed the leak(s) before I knew of VisualVM. So it might be the case that VisualVM adds additional leaks, there is definitely one (or more) present in Epsilon concordance (as it disappeared when I removed the plugins/features)
Ed Willink wrote on Wed, 26 September 2012 12:47I generally take a heap dump as soon as I have done a manual GC and then
just filter by interesting package paths.
Thanks for the hint, I'll try this and see whether it becomes more clear what causes the problems.
[Updated on: Wed, 26 September 2012 14:13] Report message to a moderator
|
|
|
Powered by
FUDForum. Page generated in 0.02227 seconds