[gregorco]

I need help understanding why the memory on my MyEclipseBlue7.0 is stuck at 64M. I’ve modified the myeclipse-blue.ini file under the C:\opt\Genuitec\MyEclipse 7.0 Blue Edition folder to look like this:
——————————————————————————————-
-startup
../Common\plugins\org.eclipse.equinox.launcher_1.0.101.R34x_v20080819.jar
–launcher.library
../Common\plugins\org.eclipse.equinox.launcher.win32.win32.x86_1.0.101.R34x_v20080731
-clean
-configuration
C:\opt\Genuitec\MyEclipse 7.0 Blue Edition\configuration
-vm
C:\opt\Genuitec\Common\binary\com.sun.java.jre.win32.x86_1.5.0.011\bin\client\jvm.dll
-vmargs
-Xms128M
-Xmx512M
-XX:PermSize=128M
-XX:MaxPermSize=512M
——————————————————————————————-

but doesn’t appear to make a difference. I was prompted to update this file after getting an OutOfMemory error popup while configuring my projects and can’t figure out what I could’ve done to cause the memory problem in the first place. Anyway – after updating the myeclipse-blue.ini file I expected to see the memory in the lower right corner of the window bump up when it got close to the initial 64M value, but it never bumps up and quickly reaches the 64M and then fails.

Where is that 64M value configured and why isn’t the myeclipse-blue.ini being respected during startup?

Thanks for your help,
Gregor

[support-joy]

Hi Gregor,

Sorry to hear that you have encountered this problem. Can you check the heap status? you can find the same under Windows > Preferences > General. Please monitor, what causes the spike in heap memory. Can you run the garbage collector, go to MyEclipse > Utilities > Run Garbage Collection.
Also can you copy paste your installation detail here? Go to MyEclipse > Installation Summary > Installation Detail.
If you are modifying the ini file, make sure there are no extra special characters like enter key, space, etc.

[gregorco]

Hi Joy,

Turns out that when I replaced my myeclipse-blue.ini with a co-worker’s “clean” version that that fixed it. I could once again open MyEclipseBlue7.0 and the memory successfully went beyond the 64M cap that was causing a problem earlier. I still don’t know what I had done to initially get the OutOfMemory error that prompted me to go alter my myeclipse-blue.ini file. I did suspect that when I modified the ini file that the trailing space character after each line that I added might have caused the problem but after recognizing that difference I removed the spaces and still had a problem. Anyway – like I said earlier after replacing my ini file with a “clean” one I was back in business. Next time I’ll be more diligent about making a backup of the original file before attempting to modify it. Thanks, Gregor.

[Riyad Kalla]

Gregor,

The platform is *super sensitive* to end of line and new line chars in those ini files — is there a chance you edited the file in a text editor that had universal/Unix newline characters set and not the default Windows ones? That will do it (As you found out).

[Author]

Posts