Another possible bug with "Switch To..." (and presumably "Update"): it looks like the history (hg log output) is cached across project close. This could cause Eclipse's memory use to grow unnecessarily. Here's how I'm reproducing it:
1) start Eclipse 2) open a project with Mercurial history (> 500 revs) 3) project right click->Team->Switch To 4) scroll *almost* to the bottom of the list to confirm only 500 revs showing 5) scroll right to the bottom to trigger loading the next 200 revs 6) repeat until all history is loaded (or you get bored) 7) cancel out of Switch To dialog 8) close the project 9) reopen the project 10) back to Team->Switch To 11) note that it ran "hg log ... -l 500" to get the first 500 revs again 12) scroll *almost* to the bottom of the list (ie. being careful not to trigger a reload) and note that it's showing as much history as you loaded in step 6 above, i.e. closing the project did *not* discard that history from memory This caching appears *not* to affect the main Team->Show History window. Do "Switch To" and "Show History" have separate history caches? Greg --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "MercurialEclipse" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/mercurialeclipse?hl=en -~----------~----~----~----~------~----~------~--~---
