Community
Participate
Working Groups
Build id: 20111215-0110 EPP package: http://build.eclipse.org/technology/epp/epp_build/juno/download/20111215-0115/20111215-0115_eclipse-linuxtools-juno-M4-linux.gtk.x86_64.tar.gz Fedora 16, x86_64 I've been testing the above EPP package. After some usage, I tried the Linux Tools GProf plugin which opens a view for .gmon files. After attempting to open this view, I got an error dialogue regarding "Java heap space" from the Project Explorer. I then changed eclipse.ini to include these lines (among others); --launcher.XXMaxPermSize 512m -vmargs -XX:MaxPermSize=512m -Xms256m -Xmx1024m When I re-launched Eclipse, the error came back immediately. It seems after clearing it and declining to shut down the workbench, I can continue usage without problems. !ENTRY org.eclipse.ui 4 4 2011-12-15 11:32:06.371 !MESSAGE An internal error has occurred. !STACK 0 java.lang.OutOfMemoryError: Java heap space at org.eclipse.ui.part.ResourceTransfer.nativeToJava(ResourceTransfer.java:162) at org.eclipse.swt.dnd.Clipboard.getContents(Clipboard.java:323) at org.eclipse.swt.dnd.Clipboard.getContents(Clipboard.java:241) at org.eclipse.ui.internal.navigator.resources.actions.PasteAction$1.run(PasteAction.java:191) at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:180) at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:150) at org.eclipse.swt.widgets.Display.syncExec(Display.java:4331) at org.eclipse.ui.internal.navigator.resources.actions.PasteAction.updateSelection(PasteAction.java:186) at org.eclipse.ui.actions.BaseSelectionListenerAction.selectionChanged(BaseSelectionListenerAction.java:124) at org.eclipse.ui.internal.navigator.resources.actions.EditActionGroup.updateActionBars(EditActionGroup.java:148) at org.eclipse.ui.internal.navigator.resources.actions.EditActionGroup.fillActionBars(EditActionGroup.java:96) at org.eclipse.ui.internal.navigator.resources.actions.EditActionProvider.fillActionBars(EditActionProvider.java:46) at org.eclipse.ui.navigator.NavigatorActionService$3.run(NavigatorActionService.java:259) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.ui.navigator.NavigatorActionService.fillActionBars(NavigatorActionService.java:253) at org.eclipse.ui.navigator.CommonNavigatorManager$2.run(CommonNavigatorManager.java:92) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.ui.navigator.CommonNavigatorManager$UpdateActionBarsJob.runInUIThread(CommonNavigatorManager.java:87) at org.eclipse.ui.progress.UIJob$1.run(UIJob.java:95) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3563) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3212) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:977) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:893) at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:91) at org.eclipse.ui.internal.Workbench$3.run(Workbench.java:565) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:520) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
I guess this makes Eclipse and/or the GProf plug-in unusable, correct?
(In reply to comment #1) > I guess this makes Eclipse and/or the GProf plug-in unusable, correct? Yes, but like I said, if I clear it and decline to restart, it seems to be usable.
This looks very much like a duplicate of https://bugs.eclipse.org/bugs/show_bug.cgi?id=205678
(In reply to Andrew Overholt from comment #0) > I then changed eclipse.ini to include these lines (among others); > > --launcher.XXMaxPermSize > 512m > -vmargs > -XX:MaxPermSize=512m > -Xms256m > -Xmx1024m Can you try with these: --launcher.XXMaxPermSize 512m --launcher.appendVmargs -vmargs -Xms256m -Xmx1024m
(In reply to Dani Megert from comment #4) > (In reply to Andrew Overholt from comment #0) > > I then changed eclipse.ini to include these lines (among others); > > > > --launcher.XXMaxPermSize > > 512m > > -vmargs > > -XX:MaxPermSize=512m > > -Xms256m > > -Xmx1024m > > > Can you try with these: > > --launcher.XXMaxPermSize > 512m > --launcher.appendVmargs > -vmargs > -Xms256m > -Xmx1024m I haven't experienced this recently so let's just close it.
This is a dup of bug 205678, fixed in 4.5. *** This bug has been marked as a duplicate of bug 205678 ***
