facebook

MyEclipse 8 PermGen Memory, SERIOUS problem

  1. MyEclipse Archived
  2.  > 
  3. Bugs
Viewing 15 posts - 1 through 15 (of 17 total)
  • Author
    Posts
  • #305996 Reply

    b_jones10634
    Member

    This message has not been recovered.

    #306028 Reply

    b_jones10634
    Member

    This message has not been recovered.

    #306032 Reply

    b_jones10634
    Member

    This message has not been recovered.

    #306033 Reply

    b_jones10634
    Member

    This message has not been recovered.

    #306050 Reply

    This message has not been recovered.

    #306069 Reply

    b_jones10634
    Member

    This message has not been recovered.

    #306088 Reply

    This message has not been recovered.

    #306095 Reply

    b_jones10634
    Member

    This message has not been recovered.

    #306116 Reply

    This message has not been recovered.

    #306126 Reply

    mcguolo
    Member

    This message has not been recovered.

    #306129 Reply

    b_jones10634
    Member

    This message has not been recovered.

    #306151 Reply

    This message has not been recovered.

    #306205 Reply

    b_jones10634
    Member

    Shalini,

    1) I’m not receiving the PermGen error since my first re-install, however that could be due to the fact that I’m not consistently watching the memory manager and running the garbage collection every time it exceeds 70% of available memory. I am still receiving Memory Pool errors, Javascript validation errors, key binding errors, etc etc…

    2) Attempted to install some ‘Examples on Demand’ in a freshly created workspace, however, none of the projects could be installed, and all failed with the message ‘Could not install example project’.

    3) I’ve also noticed that MyEclipse fails and throws an error every time I tell it to generate the serialVersionUID for a class that implements the Serializable interface. Not highly critical, but annoying none the less.

    4) This morning I started receiving another Memory error as follows:

    MyEclipse has detected that less than 5% of the 3MB of Survivor Space (Heap memory) space remains.

    It is strongly recommended that you exit and restart MyEclipse with new virtual machine
    memory paramters to increase this memory. Failure to do so can result in data loss.

    Recommended memory arguments:
    -vmargs
    -Xmx512m
    -XX:MaxPermSize=256m
    -XX:ReservedCodeCacheSize=64m

    #306211 Reply

    b_jones10634
    Member

    Here’s a new one that’s come up when editing JavaScript files:

    Exception when processing proposal for: appendTo()
    plugin: org.eclipse.wst.jsdt.ui
    Stack Trace:

    java.lang.IllegalArgumentException
    at org.eclipse.wst.jsdt.internal.core.util.Util.scanTypeSignature(Util.java:2322)
    at org.eclipse.wst.jsdt.core.Signature.getParameterCount(Signature.java:914)
    at org.eclipse.wst.jsdt.ui.text.java.CompletionProposalCollector.createMethodReferenceProposal(CompletionProposalCollector.java:737)
    at org.eclipse.wst.jsdt.ui.text.java.CompletionProposalCollector.createJavaCompletionProposal(CompletionProposalCollector.java:403)
    at org.eclipse.wst.jsdt.ui.text.java.CompletionProposalCollector.accept(CompletionProposalCollector.java:214)
    at org.eclipse.wst.jsdt.internal.codeassist.CompletionEngine.findLocalMethods(CompletionEngine.java:5629)
    at org.eclipse.wst.jsdt.internal.codeassist.CompletionEngine.findMethods(CompletionEngine.java:6727)
    at org.eclipse.wst.jsdt.internal.codeassist.CompletionEngine.findFieldsAndMethods(CompletionEngine.java:3994)
    at org.eclipse.wst.jsdt.internal.codeassist.CompletionEngine.complete(CompletionEngine.java:1787)
    at org.eclipse.wst.jsdt.internal.codeassist.CompletionEngine.complete(CompletionEngine.java:2632)
    at org.eclipse.wst.jsdt.internal.core.Openable.codeComplete(Openable.java:135)
    at org.eclipse.wst.jsdt.internal.core.CompilationUnit.codeComplete(CompilationUnit.java:306)
    at org.eclipse.wst.jsdt.internal.core.CompilationUnit.codeComplete(CompilationUnit.java:299)
    at org.eclipse.wst.jsdt.internal.ui.text.java.JavaCompletionProposalComputer.internalComputeCompletionProposals(JavaCompletionProposalComputer.java:174)
    at org.eclipse.wst.jsdt.internal.ui.text.java.JavaCompletionProposalComputer.computeCompletionProposals(JavaCompletionProposalComputer.java:142)
    at org.eclipse.wst.jsdt.internal.ui.text.java.CompletionProposalComputerDescriptor.computeCompletionProposals(CompletionProposalComputerDescriptor.java:298)
    at org.eclipse.wst.jsdt.internal.ui.text.java.CompletionProposalCategory.computeCompletionProposals(CompletionProposalCategory.java:258)
    at org.eclipse.wst.jsdt.internal.ui.text.java.ContentAssistProcessor.collectProposals(ContentAssistProcessor.java:244)
    at org.eclipse.wst.jsdt.internal.ui.text.java.ContentAssistProcessor.computeCompletionProposals(ContentAssistProcessor.java:213)
    at org.eclipse.jface.text.contentassist.ContentAssistant.computeCompletionProposals(ContentAssistant.java:1832)
    at org.eclipse.jface.text.contentassist.CompletionProposalPopup.computeProposals(CompletionProposalPopup.java:556)
    at org.eclipse.jface.text.contentassist.CompletionProposalPopup.access$16(CompletionProposalPopup.java:553)
    at org.eclipse.jface.text.contentassist.CompletionProposalPopup$2.run(CompletionProposalPopup.java:488)
    at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
    at org.eclipse.jface.text.contentassist.CompletionProposalPopup.showProposals(CompletionProposalPopup.java:482)
    at org.eclipse.jface.text.contentassist.ContentAssistant$2.run(ContentAssistant.java:376)
    at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
    at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134)
    at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3855)
    at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3476)
    at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405)
    at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369)
    at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221)
    at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500)
    at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
    at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493)
    at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
    at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113)
    at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194)
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:368)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559)
    at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
    at org.eclipse.equinox.launcher.Main.run(Main.java:1311)

    #306842 Reply

    I have the exactly the SAME issue. Every time I imported a project, I got the Indexer and memory error and have to exit MyEclipse and started again, and it repeats all the time, even I restart my PC.

Viewing 15 posts - 1 through 15 (of 17 total)
Reply To: MyEclipse 8 PermGen Memory, SERIOUS problem

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