Community
Participate
Working Groups
Reproducibility: Always. Steps: 1. Point CVS to :pserver:anonymous@cvs.fedoraproject.org:/cvs/pkgs 2. Attempt to checkout the entire rpms module. Result: It will take a long time, then Eclipse will crash. All projects do check out correctly and upon restart of Eclipse seem to work just fine. This might mean that the crash is due to some post-processing/cleanup work? If that's the case, it would be nice if there was an option to disable whatever post-processing CVS does after checkout, or automatically disable it [with warning message] after post-processing more than X projects... Your opinions would be appreciated :) Footnote: There are a lot of folders and files in rpms (over 9000 in the base directory alone).
Charley, in 3.6 there were two fixes addressing OutOfMemoryError during workspace refresh (bug 294429 and bug 292267). What build do you use?
Thanks Pawel, I'll download 3.6 M5 and report back if fixed. My current build is: Eclipse SDK Version: 3.5.2 Build id: M20100211-1343
No need to do so, both fixes I've referred were backported to 3.5.2 (bug 294707 and bug 293519). As a workaround you may go to <INSTALLATION_ROOT>/eclipse.ini and increase maximum heap size.
(In reply to comment #3) > No need to do so, both fixes I've referred were backported to 3.5.2 (bug 294707 > and bug 293519). As a workaround you may go to <INSTALLATION_ROOT>/eclipse.ini > and increase maximum heap size. Ah -- I've already been running my 3.5.2 build with extra memory (-vmargs -Xms1024m -Xmx1024m -XX:PermSize=512m -XX:MaxPermSize=512m). I note both previous bugs talk about workspaces of around 500,000 -- the rpms module in Fedora CVS that I was working with has about 1,000,000 files. I guess I am out of luck, at least for now. I'll give it a test again tonight on 3.6 M6, just in case, and report back.
Still experiencing problems under both 3.5.2 and 3.6 M6 with -Xms2048m and -Xmx2048m. The reported bugs seem to have resolved issues for workspaces with 500,000 files, but the rpms module in Fedora has about 900,000 files, so I guess it is just the difference in size... If somebody would like to take a look at this, that would be great. I suppose I will leave this bug as Open for now, though. I'll try a couple of tests in my spare time over the next few days and update this bug if anything changes :)
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.
