Community
Participate
Working Groups
I have increased the amount of memory used by Eclipse by specifying -vmargs - Xmx384M in the startup. This does help me compile my big project which is a Web Application. However if I keep recompiling the Aspect project, the memory used by Eclipse keeps growing to where eventually it says, its out of Memory. In my case, I have 512M on my laptop and I have assigned 384M to Eclipse. Any solutions?
I have just committed a fix to CVS for a serious memory leak. It does affect continuous recompiling which appears to be the issue here, basically the outline view kept asking aspectj for new versions of the view for a file, but it never told aspectj that old views were finished with and could be deleted - hence after multiple compiles, the memory runs out. This fix will be rolled into 0.5.2 which will be available relatively soon - if you are happy to pickup CVS updates and build them yourself it is available right now. I don't know if this is the only memory leak, but it is a serious one.
This should be fixed in 0.5.2.
Fixed in 0.5.2 release as per previous comments.
Seems to happen still. I downloaded the 0.5.2 version of plugin. Compiled once. memory used by Eclipse increased to approx 420M( My startup settings were for 384M). after the first compile, I hit Build again..and then at a certain point in the Build, I got the Out of memory error. Now I cant get back into Eclipse ( have filed a bug request - 23932)
Whilst working on another feature I noticed that in some cases we might be using the wrong kind of marker against some resources - some marker types persist and some don't. We might be leaking markers, in particular the markers we attach to resources when the outline view builds 'goto markers'.
We believe this is now fixed - we found a serious leak of Image resources caused by updating the outline views (e.g. after compile) and when displaying the build config editor on large projects. The fix is in the 0.6.0 stream.
