now that you mention it, this did start happening when I started
working on my Java/Hibernate code. Previously, I only used the PHP,
SVN & Flex perspectives. I changed to Xmx512m and I'll see if that
helps. I can't believe you are getting it with 1300! I am also
going to see if closing my projects while I am not working on them
helps.
- Kevin
On Apr 24, 2007, at 12:44 AM, Peter wrote:
I have it very regularly (very frustrating indeed). I have –vmargs -
Xms128m -Xmx1300m in eclipse.ini but it hardly seems related to the
Xmx value. It does seem related in my case to the fact that I am
also using the Eclipse instance to do Java and/or XML editing and/
or Java/Tomcat debugging – I almost always run into it when I
switch from a longer period of flex editing/debugging to Java (or
vice versa).
I remember reading on this list that in once case switching
automatic compilation of helped/fixed the problem. I have not tried
that though as that would probably get me in a bigger mess than
restarting every hour or so.
If you find out something I would certainly appreciate if you could
share your solution.
Thanks!
Peter
From: [email protected]
[mailto:[EMAIL PROTECTED] On Behalf Of Kevin
Sent: Tuesday, April 24, 2007 6:22 AM
To: [email protected]
Subject: [flexcoders] Ecplise Out Of Memory Errors
Is anyone getting this error when running Flex in Eclipse? "An out
of memory error has occurred. Consult the "Running Eclipse" section
of the README file...."
I have no idea what is causing this or how to fix it.
Thanks, Kevin
