For help with installation, bugs reports or feature requests, please head over to our new forums.
Genuitec Community on GitHub
- This topic has 1 reply, 2 voices, and was last updated 11 years, 8 months ago by
.
-
Posts
-
Hello,
Recently I installed MyEclipse 2014 Pro 64 bit on my Windows 8 (12 GB RAM). I copied the memory settings from MyEclipse 10 installed on my desktop as well. Everything used to work just fine with MyEclipse10, but now for the same workspace ME hangs for 10 minutes and then displays the following error: “An internal error occurred during: “Check registration”. Java heap space” and “An internal error occurred during: “MyEclipse Memory Monitor”. GC overhead limit exceeded”.There are myeclipse.ini settings:
#utf8 (do not remove)
-startup
plugins/org.eclipse.equinox.launcher_1.3.0.v20130327-1440.jar
–launcher.library
plugins/org.eclipse.equinox.launcher.i18n.win32.win32.x86_64_3.2.0.v201103301700
-vm
F:\MyEclipse\MyEclipse Pro 2014\binary\com.sun.java.jdk7.win32.x86_64_1.7.0.u45\bin\javaw.exe
-configuration
F:\MyEclipse\MyEclipse Pro 2014\configuration
-install
F:\MyEclipse\MyEclipse Pro 2014
-vmargs
-Xms256m
-XX:ReservedCodeCacheSize=256m
-Xmx1792m
-XX:MaxPermSize=1280m
-XX:ReservedCodeCacheSize=64m
-Dosgi.nls.warnings=ignoreThank you!
Nitsko,
Sorry that you are seeing this issue.
Can you please answer some more questions for us?
1. Are you opening the same MyEclipse 10 workspace in MyEclipse 2014? Is the MyEclipse 10 also installed on the Windows 8, 64 bit? Usually switching to 64 bit needs more memory.
2. How large is the workspace, in terms of number of projects and files in each project?
3. Can you please remove the duplicate entry -XX:ReservedCodeCacheSize from the myeclipse.ini file,change -Xms256m to -Xms512m and try increasing the -Xmx to a higher value and see if it fixes the issue?
4. If possible, can you please switch to a new workspace, create a dummy project and see if the issue persists ? If the issue cannot be replicated try importing the projects from the MyEclipse 10 workspace and check?
5. Please delete the contents of the .log file which is located at <workspace dir>/.metadata/.log. Now replicate the issue with the problematic workspace and attach the .log file to help us investigate further (change the .log to .txt to attach it).
Let us know how it works for you.
