OK. I'm not 100% certain that the command line will take precedence
over the eclipse.ini. You might want to edit the -Xmx512m there.
Except that with a drive letter like L:, I'm surmising that you're
running it from a network share? This may cause some significant
performance problems, and is not
It is taking precedence. Setting it to e.g. 2000M (using a 32 bit VM)
stops Eclipse from starting stating the normal could not create Java
virtual machine.
No, L: is a local disk. :)
Yes, 381.500 kB is about 381 MB .
The 32 bit VM on my OS can create a VM with more than 1GB as Xmx, the
limit is
Btw. I'm actually not sure that the problem really is an out of memory
exception. Yes, the log says so, but I think it's caused by an other
unhandled exception, and then something is catching that exception and
throws an out of memory exception. Don't know why, but that is a hunch
that I get.
I'll have to explicitly 100% agree with Bob here:
Until around mid May I was using the previous model MacBookPro with 4GB
dual core (and Ubuntu) for my Android development and after a fair
amount of tweaking I could barely run Eclipse for a week.
After switching to the new MacBookPro with
I think there's some memory leak issue if editing XML files.
I realise if I only open .java it is ok.
So maybe a temp work around is to edit xml file with editor and open
only .java in eclipse?
On Aug 4, 10:17 am, Doug beafd...@gmail.com wrote:
The issue isn't what else is running on the
I may be kicking in open doors here, but have you tried this old stuff?
http://www.luisdelarosa.com/2005/04/03/how-to-get-better-memory-settings-for-eclipse-on-mac-os-x/
For me (Ubuntu - see previous post for details) this worked fairly OK on
my old 4GB system:
eclipse -Xmx150m
This
This looks likely.
I can run Eclipse all day on a 4G Windows 64bit machine, but I edit my
layouts by hand, without the visual editor.
-- Kostya
04.08.2010 11:00, Mystique пишет:
I think there's some memory leak issue if editing XML files.
I realise if I only open .java it is ok.
So maybe a
Ah, I think I can relate to that statement: for 95+% of the XML editing
I referred to I used Eclipse itself, but like Kostya I stayed mostly in
the XML view, only an occasional glance at the graphical layout since
(at least for my cases) I decided the visual layout could not really be
trusted.
Here are the settings I changed in my eclipse.ini after encountering
this problem:
-vm
/System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home/bin/
java
-vmargs
-Dosgi.requiredJavaVersion=1.6
-XX:MaxPermSize=256m
-Xms1024m
-Xmx1024m
I can code all day long and leave Eclipse open for a
I think it was stated previously in this thread. The problem isn't
Eclipse. The problem is the Android plugin. I'm using Eclipse more
than 8h per day at work, and I don't have any problems there (I'm not
doing any Android development at work). I can also use Eclipse at home
without any problems if
On 08/04/2010 05:00 PM, Kaj Bjurman wrote:
I think it was stated previously in this thread. The problem isn't
Eclipse. The problem is the Android plugin.
I would agree on that one, I use Eclipse for Flex and although there are
other kinds of issues there, the Andorid plugins appears to be the
The Eclipse UI editor for Qt (which is similarly XML based) exhibits
similar behavior -- some things you can do OK, but certain complex
operations crash the editor (and sometimes Eclipse) with fair
regularity. You learn to save your layouts frequently.
Re poor performance in general, folks with
I just provoked my Eclipse again, just to see what the error message
is. I remembered it as out of handles, but that was a bit wrong. I
checked the process in the task manager when it was in the error
state. It isn't out of memory, and it's probably not out of handles.
The CPUs are also idle, so
OK, this is good information. You are, in fact, running out of memory
-- somehow.
I've see this, but seldom as performance starts to suck for me long
before.
How exactly are you allocating memory for Java? How are you starting
Eclipse?
And when you were checking how much memory Eclipse was
I just say 'Serenity Now' and count to 10. The layout file usually opens by
that point.
On Wed, Aug 4, 2010 at 6:44 PM, Bob Kerns r...@acm.org wrote:
OK, this is good information. You are, in fact, running out of memory
-- somehow.
I've see this, but seldom as performance starts to suck for
Eclipse is started using a shortcut:
Galileo
L:\eclipse-jee-galileo-win32\eclipse\eclipse.exe -vmargs -Xmx1324m
Ganymede
L:\eclipse\eclipse.exe -vmargs -Xmx1324m
(I'm having the same problem in both)
eclipse.ini says:
--launcher.library
(And the workspace is using 1.5.0_19)
On 5 Aug, 03:44, Bob Kerns r...@acm.org wrote:
OK, this is good information. You are, in fact, running out of memory
-- somehow.
I've see this, but seldom as performance starts to suck for me long
before.
How exactly are you allocating memory for Java?
It's long been my opinion that the minimum development environment
should be 8 GB, quad core. And, ideally, solid-state disks.
Definitely *NOT* a 5200 RPM or slower hard drive! Ever!
I run on a 4GB, dual core laptop, SATA 7200 RPM hard drive. But I've
also run on 8 GB, quad core, and know what a
The issue isn't what else is running on the computer. The issue is
that Eclipse gets into an unrecoverable state where it lags horribly
when switching between editors, at least on OSX. I can typically go 5
or 6 hours of steady use (more with intermittent use) until that state
kicks in for me
Doug, I'm surprised you can go for 5 or 6 hours. It grinds to a halt
for me in less than an hour. But I guess it depends on what you're
doing (Java vs resources).
But I'll echo what you said: it's not that the IDE is generally slow,
it's something else that is chewing up resources. It's not
You missed my point, so let me try to make it more clearly.
I wasn't absolving the IDE of blame. I'm saying it interacts with the
other offenders, if you have them.
So if you have a bloated Firefox, for example, the IDE will start to
flail much earlier. In that case, you can buy some time (but
So everyone has this issue and they just deal with it? I'm amazed to
find such a productivity killer in a platform that's been out for a
couple of years. I'm hoping we are simply unenlightened and someone
will stop by with an easy fix. :)
I'm on OS X, 4GB RAM, core 2 duo, btw, using some
Hi, you mean in OSX is the same thing?
On Aug 3, 10:51 pm, objectuser kevin.k.le...@gmail.com wrote:
So everyone has this issue and they just deal with it? I'm amazed to
find such a productivity killer in a platform that's been out for a
couple of years. I'm hoping we are simply
Yes, same issue for me. I need to restart Eclipse every few minutes
if I don't want to wait 10s to switch between Java files, etc.
On Aug 3, 10:08 am, Mystique joven.ch...@gmail.com wrote:
Hi, you mean in OSX is the same thing?
On Aug 3, 10:51 pm, objectuser kevin.k.le...@gmail.com wrote:
Doesn't happen to me.
Ubuntu Lucid, AMD Phenom II X4 945, 4GB RAM.
Emulator is slow when booting, but nothing else (I have to say that my
projects are tiny).
On Tue, Aug 3, 2010 at 5:32 PM, objectuser kevin.k.le...@gmail.com wrote:
Yes, same issue for me. I need to restart Eclipse every few
It has unfortunately been like that for ages (if you are modifying
e.g. layout files). It doesn't happen if you only write code.
It looks like the Android plugin is leaking resources, and fast.
On 30 Juli, 13:22, Mystique joven.ch...@gmail.com wrote:
Hi,
I'm on Win7 32-bit with 4GB RAM. Why
I see. I thought I'm the only one...
Yes, I look at the log and so many memory leak error...
On Jul 30, 8:55 pm, Kaj Bjurman kaj.bjur...@gmail.com wrote:
It has unfortunately been like that for ages (if you are modifying
e.g. layout files). It doesn't happen if you only write code.
It looks
27 matches
Mail list logo
