Community
Participate
Working Groups
Created attachment 283404 [details] Screenshot of leak suspects report Since 2020-06 I experience a memory leak of the IDE after around a day. Forcing the IDE to freeze. Taking a memory dump and running the "leak suspects" report with MAT, it brings up JDT.
Nothing changed in this area recently. So, I wouldn't be surprised if this is an old issue. We had a similar issue in the past that was fixed via bug 434464. But then it was fixed in 4.5 and assuming you are on Eclipse 4.16, this has to be a different issue. Jens, can you try this experiment. Can you try and reset the preference which will in turn clear the caches and observe what happens? You can try some trivial changes on the "Java Compiler -> Annotation Processing -> Factory Path" and apply.
(In reply to Jay Arthanareeswaran from comment #1) > Nothing changed in this area recently. So, I wouldn't be surprised if this > is an old issue. We had a similar issue in the past that was fixed via bug > 434464. I am working with this workspace for quite a while now, and only recently upgraded to Eclipse 2020-06. And then it started. > But then it was fixed in 4.5 and assuming you are on Eclipse 4.16, > this has to be a different issue. Yes, I think Eclipse 2020-06 means 4.16. > > Jens, can you try this experiment. Can you try and reset the preference > which will in turn clear the caches and observe what happens? You can try > some trivial changes on the "Java Compiler -> Annotation Processing -> > Factory Path" and apply. I tried to look up that setting, and I do remember that a section named "Annotation Processing" existed in the past, but now it seemed to be gone. I enabled "Store Information About Method Parameters" instead. That re-built the whole workspace. Disabled it afterwards again. I will see if that makes a change.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
