F14: after last updates, getting Eclipse out of memory errors

[Marius Andreiana]

Hi,

After getting latest updates (glibc and eclise), I started getting
reproducible Eclipse out of memory errors (happens during AppEngine
deploys). Haven't done any other changes to my env besides yum update.
Should I file a bug?

!ENTRY org.eclipse.ui 4 4 2010-11-20 15:47:18.005
!MESSAGE An internal error has occurred.
!STACK 0
java.lang.OutOfMemoryError: Java heap space
    at org.eclipse.jface.text.GapTextStore.allocate(GapTextStore.java:339)
    at org.eclipse.jface.text.GapTextStore.reallocate(GapTextStore.java:290)
    at org.eclipse.jface.text.GapTextStore.adjustGap(GapTextStore.java:223)
    at org.eclipse.jface.text.GapTextStore.replace(GapTextStore.java:196)
    at
org.eclipse.jface.text.CopyOnWriteTextStore.replace(CopyOnWriteTextStore.java:158)
    at
org.eclipse.jface.text.AbstractDocument.replace(AbstractDocument.java:1184)
    at
org.eclipse.jface.text.AbstractDocument.replace(AbstractDocument.java:1210)
    at
org.eclipse.ui.internal.console.ConsoleDocument.replace(ConsoleDocument.java:82)
    at
org.eclipse.ui.internal.console.IOConsolePartitioner.processQueue(IOConsolePartitioner.java:572)
    at
org.eclipse.ui.internal.console.IOConsolePartitioner$QueueProcessingJob.runInUIThread(IOConsolePartitioner.java:520)
    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:134)
    at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3515)
    at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3164)
    at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2640)
    at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2604)
    at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438)
    at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671)
    at
org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
    at
org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664)
    at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
    at
org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115)
    at
org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
    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:369)
    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:57)
    at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:616)

!ENTRY org.eclipse.ui 4 4 2010-11-20 15:47:22.987
!MESSAGE An internal error has occurred.
!STACK 0
java.lang.OutOfMemoryError: Java heap space
    at org.eclipse.jface.text.GapTextStore.allocate(GapTextStore.java:339)
    at org.eclipse.jface.text.GapTextStore.reallocate(GapTextStore.java:290)
    at org.eclipse.jface.text.GapTextStore.adjustGap(GapTextStore.java:223)
    at org.eclipse.jface.text.GapTextStore.replace(GapTextStore.java:196)
    at
org.eclipse.jface.text.CopyOnWriteTextStore.replace(CopyOnWriteTextStore.java:158)
    at
org.eclipse.jface.text.AbstractDocument.replace(AbstractDocument.java:1184)
    at
org.eclipse.jface.text.AbstractDocument.replace(AbstractDocument.java:1210)
    at
org.eclipse.ui.internal.console.ConsoleDocument.replace(ConsoleDocument.java:82)
    at
org.eclipse.ui.internal.console.IOConsolePartitioner.processQueue(IOConsolePartitioner.java:572)
    at
org.eclipse.ui.internal.console.IOConsolePartitioner$QueueProcessingJob.runInUIThread(IOConsolePartitioner.java:520)
    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:134)
    at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3515)
    at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3164)
    at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)
    at org.eclipse.jface.window.Window.open(Window.java:801)
    at org.eclipse.jface.dialogs.MessageDialog.open(MessageDialog.java:334)
    at
org.eclipse.ui.internal.ide.dialogs.InternalErrorDialog.open(InternalErrorDialog.java:80)
    at
org.eclipse.ui.internal.ide.IDEWorkbenchErrorHandler.openQuestionDialog(IDEWorkbenchErrorHandler.java:199)
    at
org.eclipse.ui.internal.ide.IDEWorkbenchErrorHandler.handleException(IDEWorkbenchErrorHandler.java:154)
    at
org.eclipse.ui.internal.ide.IDEWorkbenchErrorHandler.access$0(IDEWorkbenchErrorHandler.java:146)
    at
org.eclipse.ui.internal.ide.IDEWorkbenchErrorHandler$1.runInUIThread(IDEWorkbenchErrorHandler.java:121)
    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:134)
    at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3515)
    at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3164)
    at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2640)
    at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2604)
    at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438)
    at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671)

[Aleksandar Kurtakov]

On 10:05:21 am Sunday, November 21, 2010 Marius Andreiana wrote:
>  Hi,
>  
>  After getting latest updates (glibc and eclise), I started getting
>  reproducible Eclipse out of memory errors (happens during AppEngine
>  deploys). Haven't done any other changes to my env besides yum update.
>  Should I file a bug? 
Just edit /etc/eclipse.ini and set the 
--launcher.XXMaxPermSize and -Xmx384m
to something meaningful for you. JVM can allocate more memory than a predefined 
value which can be controlled by startup parameters. This is what we do in 
eclipse.ini but we can not set this to something really big because people can 
use eclipse for things that even require less than the current settings.

Alexander Kurtakov

>  
>  !ENTRY org.eclipse.ui 4 4 2010-11-20 15:47:18.005
>  !MESSAGE An internal error has occurred.
>  !STACK 0
>  java.lang.OutOfMemoryError: Java heap space
>      at org.eclipse.jface.text.GapTextStore.allocate(GapTextStore.java:339)
>      at
>  org.eclipse.jface.text.GapTextStore.reallocate(GapTextStore.java:290) at
>  org.eclipse.jface.text.GapTextStore.adjustGap(GapTextStore.java:223) at
>  org.eclipse.jface.text.GapTextStore.replace(GapTextStore.java:196) at
>  org.eclipse.jface.text.CopyOnWriteTextStore.replace(CopyOnWriteTextStore.ja
>  va:158) at
>  org.eclipse.jface.text.AbstractDocument.replace(AbstractDocument.java:1184)
>      at
>  org.eclipse.jface.text.AbstractDocument.replace(AbstractDocument.java:1210)
>      at
>  org.eclipse.ui.internal.console.ConsoleDocument.replace(ConsoleDocument.jav
>  a:82) at
>  org.eclipse.ui.internal.console.IOConsolePartitioner.processQueue(IOConsole
>  Partitioner.java:572) at
>  org.eclipse.ui.internal.console.IOConsolePartitioner$QueueProcessingJob.run
>  InUIThread(IOConsolePartitioner.java:520) 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:134
>  ) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3515) at
>  org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3164) at
>  org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2640) at
>  org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2604) at
>  org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438) at
>  org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671) at
>  org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332
>  ) at
>  org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664)
>      at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
>      at
>  org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication
>  .java:115) at
>  org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java
>  :196) at
>  org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication
>  (EclipseAppLauncher.java:110) at
>  org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseA
>  ppLauncher.java:79) at
>  org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369
>  ) 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:5
>  7) at
>  sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImp
>  l.java:43) at java.lang.reflect.Method.invoke(Method.java:616)
>  
>  !ENTRY org.eclipse.ui 4 4 2010-11-20 15:47:22.987
>  !MESSAGE An internal error has occurred.
>  !STACK 0
>  java.lang.OutOfMemoryError: Java heap space
>      at org.eclipse.jface.text.GapTextStore.allocate(GapTextStore.java:339)
>      at
>  org.eclipse.jface.text.GapTextStore.reallocate(GapTextStore.java:290) at
>  org.eclipse.jface.text.GapTextStore.adjustGap(GapTextStore.java:223) at
>  org.eclipse.jface.text.GapTextStore.replace(GapTextStore.java:196) at
>  org.eclipse.jface.text.CopyOnWriteTextStore.replace(CopyOnWriteTextStore.ja
>  va:158) at
>  org.eclipse.jface.text.AbstractDocument.replace(AbstractDocument.java:1184)
>      at
>  org.eclipse.jface.text.AbstractDocument.replace(AbstractDocument.java:1210)
>      at
>  org.eclipse.ui.internal.console.ConsoleDocument.replace(ConsoleDocument.jav
>  a:82) at
>  org.eclipse.ui.internal.console.IOConsolePartitioner.processQueue(IOConsole
>  Partitioner.java:572) at
>  org.eclipse.ui.internal.console.IOConsolePartitioner$QueueProcessingJob.run
>  InUIThread(IOConsolePartitioner.java:520) 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:134
>  ) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3515) at
>  org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3164) at
>  org.eclipse.jface.window.Window.runEventLoop(Window.java:825) at
>  org.eclipse.jface.window.Window.open(Window.java:801)
>      at org.eclipse.jface.dialogs.MessageDialog.open(MessageDialog.java:334)
>      at
>  org.eclipse.ui.internal.ide.dialogs.InternalErrorDialog.open(InternalErrorD
>  ialog.java:80) at
>  org.eclipse.ui.internal.ide.IDEWorkbenchErrorHandler.openQuestionDialog(IDE
>  WorkbenchErrorHandler.java:199) at
>  org.eclipse.ui.internal.ide.IDEWorkbenchErrorHandler.handleException(IDEWor
>  kbenchErrorHandler.java:154) at
>  org.eclipse.ui.internal.ide.IDEWorkbenchErrorHandler.access$0(IDEWorkbenchE
>  rrorHandler.java:146) at
>  org.eclipse.ui.internal.ide.IDEWorkbenchErrorHandler$1.runInUIThread(IDEWor
>  kbenchErrorHandler.java:121) 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:134
>  ) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3515) at
>  org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3164) at
>  org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2640) at
>  org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2604) at
>  org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438) at
>  org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671)

[Marius Andreiana]

On Mon, Nov 22, 2010 at 10:08 AM, Alexander Kurtakov <akurtako(a)redhat.com&gt;wrote:

>  On 10:05:21 am Sunday, November 21, 2010 Marius Andreiana wrote:
>  > Hi,
>  >
>  > After getting latest updates (glibc and eclise), I started getting
>  > reproducible Eclipse out of memory errors (happens during AppEngine
>  > deploys). Haven't done any other changes to my env besides yum update.
>  > Should I file a bug?
>
>  Just edit /etc/eclipse.ini and set the
>  --launcher.XXMaxPermSize and -Xmx384m
>  to something meaningful for you. JVM can allocate more memory than a
>  predefined
>  value which can be controlled by startup parameters. This is what we do in
>  eclipse.ini but we can not set this to something really big because people
>  can
>  use eclipse for things that even require less than the current settings.
>
>  Alexander Kurtakov
>  
solved, thanks!