- This topic has 10 replies, 3 voices, and was last updated 20 years, 6 months ago by
.
-
Posts
-
Hello,
more than once a day I get an “out of memory” when I do run “MyEclipse->Run XDoclet”, forcing me to restart Eclipse.
AFAIK you run an ant script that does the work. And Ant allows forking.
Can I configure MyEclipse to fork when running XDoclet / Ant?
thanx!
MarcusMarcus,
I’ve checked with Scott/Michael aboutt his, but in the mean time you can give more memory to Eclipse via the “-vmargs” command line argument, something like this:eclipse.exe -vmargs -Xms64m -Xmx128m@support-rkalla wrote:
Marcus,
I’ve checked with Scott/Michael aboutt his, but in the mean time you can give more memory to Eclipse via the “-vmargs” command line argument, something like this:eclipse.exe -vmargs -Xms64m -Xmx128mfunny, my args are already:
-vmargs -Xconcurrentio -Xms640m -Xmx640m@scott wrote:
The answer is “no” in Eclipse 2.1 and “yes, automatically” in 3.0M6.
oh, unfortunately I am forced to use 2.1 …
thanx!
MarcusOut of curiosity, are you really intending to give Eclipse 640M on initial startup? Does the JVM appear to take up this much ram? I’m wondering if the numbers are being ignored. Just for kicks, can you remove the -Xconcurrentio flag and change the memory args to -Xms128M -Xmx640M?
Also, I just executed ‘java -X’ on my 1.4.2_01 installation and -Xconcurrentio does not appear to be a valid flag. Is this an old one that has gone away?
@scott wrote:
Out of curiosity, are you really intending to give Eclipse 640M on initial startup? Does the JVM appear to take up this much ram?
Well, on my last job we had many thousand classes in memory, so …
But now I started from scratch again (new employer), so I could lower these values.@scott wrote:
I’m wondering if the numbers are being ignored. Just for kicks, can you remove the -Xconcurrentio flag and change the memory args to -Xms128M -Xmx640M?
Doesn’t seem to change the behaviour. The -Xmx640M has an interesting Effekt: when I do Help -> About Eclipse Platform -> Configuration Details, javaw.exe grows from ~80000k to ~688000k and Eclipse ends with an Out of memory error. I tried this again and again.
I am using always the same values for -Xms and -Xmx, because I read somewhere that this improves Java performance …
Then I reduced the two values to 256M. Pressing the “Configuration Details” button, javaw.exe grows to ~300000K and Eclipse does not colapse. An empty page is displayed. Hmm, strange. By the way: I am using Eclipse 2.1.2.
@scott wrote:
Also, I just executed ‘java -X’ on my 1.4.2_01 installation and -Xconcurrentio does not appear to be a valid flag. Is this an old one that has gone away?
Possible. Thanks for that hint!
Marcus
Marcus this is very strange indeed and sounds awefully memory-leaky… what JDK version are you using? Are you on Windows XP? 2k?
@support-rkalla wrote:
Marcus this is very strange indeed and sounds awefully memory-leaky… what JDK version are you using? Are you on Windows XP? 2k?
Windows XP
JDK 1.4.2_03Cheers!
Marcus@support-scott wrote:
The answer is “no” in Eclipse 2.1 and “yes, automatically” in 3.0M6.
This week I upgraded to Eclipse 3. Again I had these out of mem problems. Forking is not done automatically there: one has to select “Separate JRE” in the “Builders” config of a project. No out of mem anymore 🙂
Marcus
