facebook

MYeclipse 9.0 (64 bit) crashing

  1. MyEclipse IDE
  2.  > 
  3. Spring Development
Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #315732 Reply

    rpsarathy_80
    Member

    I have tried changing .init file memory setting. It doesn’t help. When ever it is building. I get crashed. Need help

    !ENTRY org.eclipse.core.jobs 4 2 2011-04-04 10:28:30.165
    !MESSAGE An internal error occurred during: “Building workspace”.
    !STACK 0
    java.lang.OutOfMemoryError: Java heap space
    at org.eclipse.wst.jsdt.internal.compiler.parser.Scanner.getLineEnds(Scanner.java:539)
    at org.eclipse.wst.jsdt.internal.compiler.parser.Parser.problemReporter(Parser.java:6305)
    at org.eclipse.wst.jsdt.internal.compiler.parser.Parser.consumeToken(Parser.java:4351)
    at org.eclipse.wst.jsdt.internal.compiler.parser.Parser.parse(Parser.java:5710)
    at org.eclipse.wst.jsdt.internal.compiler.parser.Parser.parse(Parser.java:6006)
    at org.eclipse.wst.jsdt.internal.compiler.parser.Parser.parse(Parser.java:5958)
    at org.eclipse.wst.jsdt.internal.compiler.parser.Parser.dietParse(Parser.java:4562)
    at org.eclipse.wst.jsdt.internal.compiler.Compiler.accept(Compiler.java:221)
    at org.eclipse.wst.jsdt.internal.compiler.lookup.LookupEnvironment.addUnitsContainingBinding(LookupEnvironment.java:170)
    at org.eclipse.wst.jsdt.internal.compiler.lookup.CompilationUnitScope.buildTypeBindings(CompilationUnitScope.java:342)
    at org.eclipse.wst.jsdt.internal.compiler.lookup.LookupEnvironment.buildTypeBindings(LookupEnvironment.java:244)
    at org.eclipse.wst.jsdt.internal.compiler.Compiler.accept(Compiler.java:226)
    at org.eclipse.wst.jsdt.internal.compiler.lookup.LookupEnvironment.addUnitsContainingBinding(LookupEnvironment.java:170)
    at org.eclipse.wst.jsdt.internal.compiler.lookup.CompilationUnitScope.buildTypeBindings(CompilationUnitScope.java:342)
    at org.eclipse.wst.jsdt.internal.compiler.lookup.LookupEnvironment.buildTypeBindings(LookupEnvironment.java:244)
    at org.eclipse.wst.jsdt.internal.compiler.Compiler.accept(Compiler.java:226)
    at org.eclipse.wst.jsdt.internal.compiler.lookup.LookupEnvironment.addUnitsContainingBinding(LookupEnvironment.java:170)
    at org.eclipse.wst.jsdt.internal.compiler.lookup.CompilationUnitScope.buildTypeBindings(CompilationUnitScope.java:342)
    at org.eclipse.wst.jsdt.internal.compiler.lookup.LookupEnvironment.buildTypeBindings(LookupEnvironment.java:244)
    at org.eclipse.wst.jsdt.internal.compiler.Compiler.accept(Compiler.java:226)
    at org.eclipse.wst.jsdt.internal.compiler.lookup.LookupEnvironment.addUnitsContainingBinding(LookupEnvironment.java:170)
    at org.eclipse.wst.jsdt.internal.compiler.lookup.CompilationUnitScope.buildTypeBindings(CompilationUnitScope.java:342)
    at org.eclipse.wst.jsdt.internal.compiler.lookup.LookupEnvironment.buildTypeBindings(LookupEnvironment.java:244)
    at org.eclipse.wst.jsdt.internal.compiler.Compiler.accept(Compiler.java:226)
    at org.eclipse.wst.jsdt.internal.compiler.lookup.LookupEnvironment.askForBinding(LookupEnvironment.java:205)
    at org.eclipse.wst.jsdt.internal.compiler.lookup.LookupEnvironment.askForType(LookupEnvironment.java:129)
    at org.eclipse.wst.jsdt.internal.compiler.lookup.LookupEnvironment.getType(LookupEnvironment.java:666)
    at org.eclipse.wst.jsdt.internal.compiler.lookup.LookupEnvironment.getResolvedType(LookupEnvironment.java:620)
    at org.eclipse.wst.jsdt.internal.compiler.lookup.Scope.getJavaLangFunction(Scope.java:1757)
    at org.eclipse.wst.jsdt.internal.compiler.lookup.FunctionTypeBinding.<init>(FunctionTypeBinding.java:26)
    at org.eclipse.wst.jsdt.internal.compiler.lookup.MethodBinding.createFunctionTypeBinding(MethodBinding.java:600)
    at org.eclipse.wst.jsdt.internal.compiler.lookup.MethodScope.createMethod(MethodScope.java:254)

    #315734 Reply

    cconway
    Member

    What do you have for the memory settings? Were you presented with a dialog that suggested some settings before it crashed?

    #315735 Reply

    cconway
    Member

    I’ve verified that the memory warning dialog that I was speaking about actually tells me to use the recommended sizes of:

    -vmargs
    -Xmx512m
    -XX:MaxPermSize=256m
    -XX:ReservedCodeCacheSize=64m

    Which exactly matches my default sizes from the basic install. I get the warning dialog after creating a few projects in the workspace and then trying to install the Google plugin from the Software Configuration Center. I only see this on my 64 bit windows laptop.

    I doubled both the maximum extent and maximum perm size and I don’t get the memory warning dialog anymore. Could you please try to use these memory settings in your .ini file and report back as to whether they solved your problem?

    -vmargs
    -Xmx1024m
    -XX:MaxPermSize=512m
    -XX:ReservedCodeCacheSize=64m

    #317195 Reply

    charlie.park
    Participant

    I am using Mac and do you know where I can find this .ini file for MES9.0? I looked all over the place but I can not find it…
    Thanks for your advice.

    #317371 Reply

    jkennedy
    Member

    Sorry for the delay Charlie, did you find the file.
    You will need to “Show Package Contents” on two of the files in the installation to navigate down to this file.
    The location should be something like: /Applications/MyEclipse for Spring/MyEclipse for Spring 9.app/Contents/Profile/myeclipseforspring.app/Contents/MacOS

    Let me know if you can’t find it there.

    Thanks,
    Jack

    Let me know if you don’t see the file.

Viewing 5 posts - 1 through 5 (of 5 total)
Reply To: MYeclipse 9.0 (64 bit) crashing

You must be logged in to post in the forum log in