After updating to 3.0.1 build 1002 I get this alert upon starting Eclipse: "Not enough memory. To use FDT you should raise the available memory for eclipse. Edit the file 'eclipse.ini' inside the eclipse installation directory and add the line: -Xmx512m After doing so restart eclipse."

Is this the actual FDT installation methodology, to ask the user to hand edit application init files? Or is this some bug?

Does adding a line with "-Xmx512m" to the 'eclipse.ini' file constitute an increase in memory, or are these 2 separate activities the end-user has to perform to remove the alert? As far as I know, in Mac OS X one cannot allocate memory manually for applications anymore. I have a Dual Core 2.4 GHz Macbook pro with 4 Gb RAM.

Hello Isaac,

adding a line with "-Xmx512m" to the 'eclipse.ini' file is exactly what FDT wants you to do.

We will change "Not enough memory." to "Not enough memory assigned to Eclipse" then it's more clear.

Greets, Nico.

I had the same problem this morning and think it is something broken in the build because adding the config line didn't help but downloading and installing the zip manually worked fine... Maybe it was the same problem mentioned here?

http://www.powerflasher.com/fdt/forum/v ... php?t=1793

Changing the config file and the zip file didn't get rid of this error. I'm on OSX Leopard.

Is there solution to this?

In addition, I already have the line -Xmx768m and I get the error as well. Eclipse 3.3 and OSX 10.4

i don't seem to have any file on my eclipse installation folder (i also performed a general search through the whole HD) named "eclipse.ini"
could it be the file "config.ini", found in eclipse/configuration?

my specs:
eclipse 3.3.3.1
fdt 3.0.1.1002
mac osx 10.4.10 intel

"eclipse.ini" is here: .../eclipse/Eclipse.app/Contents/MacOS/eclipse.ini.
go to the eclipse installation folder, right-click on Eclipse.app and choose "Show Package Contents", then navigate through the above mentioned path

Thanks matteomenapace for mentioning the location of eclipse.ini. It worked.

Cheers!

yes! thanks so much also from me matteomenapace. the location of this file was puzzling me. problems solved.

I get the same error:

"Not enough memory. To use FDT you should raise the available memory for eclipse. Edit the file 'eclipse.ini' inside the eclipse installation directory and add the line: -Xmx512m After doing so restart eclipse."

I've added the line to my ini, I've replaced the original (-Xmx256m) line and I've also tried adding the 512 version alongside it, but nothing seems to work. Whenever I open FDT within Eclipse I get this error message. To compound the problem, I also get the dialog box saying this this is a trial version of FDT, which I can't then dismiss, so I have to go into Task Manager to force Eclipse to close down.

I'm running Windows Vista, and my Eclipse.ini is as follows:



HELP!

I would suggest to create a new "eclipse.ini" (do NOT copy it) and type in the lines (again: NOT copy). Start with only

and try to start eclipse. Maybe there is an encoding problem with the file or somethink like that. If eclipse can't read the file (for whatever reason) it silently ignores it. Not very nice but true. And if it ignores the file the default memory is to small.

I tried that, and it didn't help. But it did guide me to the correct solution...

the problem isn't with FDT, or even with Eclipse, it's a Vista problem. I decided to create my Eclipse directory inside "c:\Program Files" because, call me anal, it seems like a good place to keep program files. Apparently not, because all of the files under there can only be accessed with administrator privileges (I wondered why I had to keep editing the ini file as administrator).

Presumably Eclipse, as it wasn't running with administrator privileges, couldn't access the ini file, so it "silently ignored it".

I re-installed Eclipse at a different location and everything works fine now.

Thanks for the pointer!

same here.
still no answer found in the forum.
@flashrelief: did you find something out?

tnx a lot in advance

I had the same problem and I managed to fix it. Here's what my config.ini file looked like by default, before I did anything to it:

marcus.geduld@blogformgroup.com

-showsplash
org.eclipse.platform
-startup
../../../plugins/org.eclipse.equinox.launcher_1.0.101.R34x_v20080819.jar
--launcher.library
../../../plugins/org.eclipse.equinox.launcher.carbon.macosx_1.0.101.R34x_v20080731
-vmargs
-Xdock:icon=../Resources/Eclipse.icns
-XstartOnFirstThread
-Xms40m
-Xmx256m
-XX:MaxPermSize=256m
-Dosgi.requiredJavaVersion=1.5
-Dorg.eclipse.swt.internal.carbon.smallFonts

The first thing I tried was adding -Xmx512m to the top of the file. That didn't work. I still got the out-of-memory error. I don't know anything about this ini file or its language, but after staring at it for a moment, I wondered if the lower-down -Xmx256m statement was overriding the one I added up top. So I deleted what I'd added and added it back to the bottom of the file. That did the trick.

I actually got this working be setting up to 1024Mb for extended memory heap (instead of just 512) and 512 for initial heap size. If nothing else helps, give it a try: