Community
Participate
Working Groups
I have a big problem when using the Local History feature, the CPU usage grows bigger and bigger (I have an Athlon 2800+ and 768 megs of RAM) and Eclipse lags horribly ('Computing Differences...')! I'm not sure if the memory is affected but it's mainly a CPU consumption problem (if there is a memory leak it's not big I think...). The problem do not appear the first time I use the Local History but at the second time and later... Then when I'm able to close the Local History, Eclipse takes so much CPU time I have to close (when possible, sometimes I have to kill it...) and restart it! To reproduce the problem, take a big source file (at least 2000+ lines), modify it heavily with repeated saves in a long time span in order to build a big history then try to open the Local History at least twice (on a big part, for example the class, not just a single method)... Note that the problem was already present in Eclipse 2.1.*.
By the "computing differences" label it looks like this is caused by the text diff algorithm. I believe it is a known issue that it performs poorly on large files with many changes. Some improvements were made in this area for 3.0. Moving to compare component for further comment.
If this is not a performance issue please remove the performance keyword as we are now tracking these more closely.
Adding my name to the cc list as we are now tracking performance issues more closely. Please remove the performance keyword if this is not a performance bug.
It sounds like there should be another PR that covers the "known issue" described by John. I searched briefly for one, but did not see it. If so, please mark this one as a dup and close. If not, this one should be anotated with the description of the issue.
*** This bug has been marked as a duplicate of 92561 ***
