Bug 33836 - GTK 2.2.1 eclipse is frozen ( error message in .log file: out of memory )
Summary: GTK 2.2.1 eclipse is frozen ( error message in .log file: out of memory )
Status: RESOLVED DUPLICATE of bug 33652
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 2.1   Edit
Hardware: PC Linux-GTK
: P1 blocker (vote)
Target Milestone: ---   Edit
Assignee: Felipe Heidrich CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-03-05 09:52 EST by Vasudeva Martin CLA
Modified: 2003-03-12 14:19 EST (History)
4 users (show)

See Also:


Attachments
workspace which freezes in Eclipse (RC1) after starting it. (986.22 KB, application/octet-stream)
2003-03-10 12:07 EST, Vasudeva Martin CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Vasudeva Martin CLA 2003-03-05 09:52:42 EST
After great help ( problems solved / many thanks for this ) for my first two
announced bugs, i will continue bug reporting. 
Eclipse sometimes stop reacting on any input ( mouse or keyboard ) The only
thing that works most time anyway is the icon( "x" ) to close eclipse. Then the
message box "Confirm exit" appears. But if I press Ok, eclipse will not close.
But somtimes eclipse get's live back and i can continue using it. 
If this dosn't work I have to kill eclipse with "<Strg>+<Alt>+<Esc>".
After starting Eclipse again, sometimes it works fine, other times it freeze in
 at once. The worst case is when eclipse freeze in after changing some sources
without saving.

In the log file there is the following Error:

< Error >
"java.lang.OutOfMemoryError: unable to create new native thread"
</ Error >

I can't belive that memory is really a problem, because i'm working on a very
small project and started Eclipse with the parameter for additional memory:

"$ECLIPSE/eclipse -vm $JAVA_PATH -data $WORKSPACE -vmargs -Xmx256M"

After i started eclipse. Ktop tells me, that there is more than 650 MB free.

Here is some Information about my System:
I'm using Suse Linux 7.3
kernel version 2.4.20
1 GHz Athlon with 1 GB RAM

For my Eclipse Installation, i installed the following files:

eclipse-SDK-RC1-linux-gtk.zip
org.eclipse.cdt-200212181139-linux-gtk_1.0.1.bin.dist.zip
org.eclipse.cdt-linux-gtk_1.0.1.bin.dist.zip
atk-1.2.0.tar.bz2
pango-1.0.5.tar.bz2
pango-1.2.1.tar.bz2
glib-2.2.1.tar.bz2
gtk+-2.2.1.tar.bz2
pkgconfig-0.14.0.tar.gz
tiff-v3.5.7.tar.gz
jpegsrc.v6b.tar.gz
libpng-1.2.5.tar.gz
j2sdk-1_4_1_01-linux-i586-rpm.bin
j2sdk-1_4_1-doc.zip
gdb-5.3.tar.gz      

I installed the above mentioned file
"org.eclipse.cdt-200212181139-linux-gtk_1.0.1.bin.dist.zip"
after i recognized that in the install configuration of the 
"Eclipse C/C++ Development Tools 1.0.1" was somthing wrong. When i viewed the
"Detail" from "Show Status" menu, i get the information, that the feature is not
 properly configured. After installing the File this mistake was gone.
But my main error described at the top unfortunately stays.

Ok, here are some sessions of the log file with the error:

< Log-File >
!ENTRY org.eclipse.ui 4 4 Mrz 05, 2003 12:13:13.717
!MESSAGE Unhandled exception caught in event loop.
!ENTRY org.eclipse.ui 4 0 Mrz 05, 2003 12:13:13.719
!MESSAGE Failed to execute runnable (java.lang.OutOfMemoryError: unable to
create new native thread)
!STACK 0
org.eclipse.swt.SWTException: Failed to execute runnable
(java.lang.OutOfMemoryError: unable to create new native thread)
	at org.eclipse.swt.SWT.error(SWT.java:2316)
	at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:97)
	at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:1484)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1327)
	at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1271)
	at org.eclipse.ui.internal.Workbench.run(Workbench.java:1254)
	at
org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:845)
	at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461)
	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:324)
	at org.eclipse.core.launcher.Main.basicRun(Main.java:247)
	at org.eclipse.core.launcher.Main.run(Main.java:703)
	at org.eclipse.core.launcher.Main.main(Main.java:539)
!ENTRY org.eclipse.ui 4 4 Mrz 05, 2003 12:13:13.722
!MESSAGE 
*** Stack trace of contained exception ***
!ENTRY org.eclipse.ui 4 0 Mrz 05, 2003 12:13:13.724
!MESSAGE unable to create new native thread
!STACK 0
java.lang.OutOfMemoryError: unable to create new native thread
	at java.lang.Thread.start(Native Method)
	at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:254)
	at org.eclipse.jface.window.ApplicationWindow$1.run(ApplicationWindow.java:431)
	at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:65)
	at org.eclipse.jface.window.ApplicationWindow.run(ApplicationWindow.java:428)
	at org.eclipse.ui.internal.WorkbenchWindow.run(WorkbenchWindow.java:1363)
	at
org.eclipse.update.internal.ui.views.ConfigurationView.getFeatures(ConfigurationView.java:1179)
	at
org.eclipse.update.internal.ui.views.ConfigurationView.access$6(ConfigurationView.java:1133)
	at
org.eclipse.update.internal.ui.views.ConfigurationView$LocalSiteProvider.getChildren(ConfigurationView.java:209)
	at
org.eclipse.jface.viewers.AbstractTreeViewer.getRawChildren(AbstractTreeViewer.java:643)
	at
org.eclipse.jface.viewers.StructuredViewer.getFilteredChildren(StructuredViewer.java:454)
	at
org.eclipse.jface.viewers.StructuredViewer.getSortedChildren(StructuredViewer.java:555)
	at
org.eclipse.jface.viewers.AbstractTreeViewer.updateChildren(AbstractTreeViewer.java:1282)
	at
org.eclipse.jface.viewers.AbstractTreeViewer.internalRefresh(AbstractTreeViewer.java:925)
	at
org.eclipse.jface.viewers.AbstractTreeViewer.internalRefresh(AbstractTreeViewer.java:934)
	at
org.eclipse.jface.viewers.AbstractTreeViewer.internalRefresh(AbstractTreeViewer.java:934)
	at
org.eclipse.jface.viewers.AbstractTreeViewer.internalRefresh(AbstractTreeViewer.java:895)
	at
org.eclipse.jface.viewers.AbstractTreeViewer.internalRefresh(AbstractTreeViewer.java:881)
	at org.eclipse.jface.viewers.StructuredViewer$7.run(StructuredViewer.java:858)
	at
org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:798)
	at org.eclipse.jface.viewers.StructuredViewer.refresh(StructuredViewer.java:856)
	at org.eclipse.jface.viewers.StructuredViewer.refresh(StructuredViewer.java:818)
	at
org.eclipse.update.internal.ui.views.ConfigurationView$4.run(ConfigurationView.java:456)
	at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:31)
	at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:94)
	at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:1484)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1327)
	at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1271)
	at org.eclipse.ui.internal.Workbench.run(Workbench.java:1254)
	at
org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:845)
	at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461)
	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:324)
	at org.eclipse.core.launcher.Main.basicRun(Main.java:247)
	at org.eclipse.core.launcher.Main.run(Main.java:703)
	at org.eclipse.core.launcher.Main.main(Main.java:539)
!ENTRY org.eclipse.ui 4 4 Mrz 05, 2003 12:13:13.784
!MESSAGE Unhandled exception caught in event loop.
!ENTRY org.eclipse.ui 4 0 Mrz 05, 2003 12:13:13.785
!MESSAGE Failed to execute runnable (java.lang.OutOfMemoryError: unable to
create new native thread)
!STACK 0
org.eclipse.swt.SWTException: Failed to execute runnable
(java.lang.OutOfMemoryError: unable to create new native thread)
	at org.eclipse.swt.SWT.error(SWT.java:2316)
	at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:97)
	at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:1484)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1327)
	at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1271)
	at org.eclipse.ui.internal.Workbench.run(Workbench.java:1254)
	at
org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:845)
	at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461)
	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:324)
	at org.eclipse.core.launcher.Main.basicRun(Main.java:247)
	at org.eclipse.core.launcher.Main.run(Main.java:703)
	at org.eclipse.core.launcher.Main.main(Main.java:539)
!ENTRY org.eclipse.ui 4 4 Mrz 05, 2003 12:13:13.788
!MESSAGE 
*** Stack trace of contained exception ***
!ENTRY org.eclipse.ui 4 0 Mrz 05, 2003 12:13:13.790
!MESSAGE unable to create new native thread
!STACK 0
java.lang.OutOfMemoryError: unable to create new native thread
	at java.lang.Thread.start(Native Method)
	at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:254)
	at org.eclipse.jface.window.ApplicationWindow$1.run(ApplicationWindow.java:431)
	at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:65)
	at org.eclipse.jface.window.ApplicationWindow.run(ApplicationWindow.java:428)
	at org.eclipse.ui.internal.WorkbenchWindow.run(WorkbenchWindow.java:1363)
	at
org.eclipse.update.internal.ui.views.ConfigurationView.getFeatures(ConfigurationView.java:1179)
	at
org.eclipse.update.internal.ui.views.ConfigurationView.access$6(ConfigurationView.java:1133)
	at
org.eclipse.update.internal.ui.views.ConfigurationView$LocalSiteProvider.getChildren(ConfigurationView.java:209)
	at
org.eclipse.jface.viewers.AbstractTreeViewer.getRawChildren(AbstractTreeViewer.java:643)
	at
org.eclipse.jface.viewers.StructuredViewer.getFilteredChildren(StructuredViewer.java:454)
	at
org.eclipse.jface.viewers.StructuredViewer.getSortedChildren(StructuredViewer.java:555)
	at
org.eclipse.jface.viewers.AbstractTreeViewer.updateChildren(AbstractTreeViewer.java:1282)
	at
org.eclipse.jface.viewers.AbstractTreeViewer.internalRefresh(AbstractTreeViewer.java:925)
	at
org.eclipse.jface.viewers.AbstractTreeViewer.internalRefresh(AbstractTreeViewer.java:934)
	at
org.eclipse.jface.viewers.AbstractTreeViewer.internalRefresh(AbstractTreeViewer.java:934)
	at
org.eclipse.jface.viewers.AbstractTreeViewer.internalRefresh(AbstractTreeViewer.java:895)
	at
org.eclipse.jface.viewers.AbstractTreeViewer.internalRefresh(AbstractTreeViewer.java:881)
	at org.eclipse.jface.viewers.StructuredViewer$7.run(StructuredViewer.java:858)
	at
org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:798)
	at org.eclipse.jface.viewers.StructuredViewer.refresh(StructuredViewer.java:856)
	at org.eclipse.jface.viewers.StructuredViewer.refresh(StructuredViewer.java:818)
	at
org.eclipse.update.internal.ui.views.ConfigurationView$4.run(ConfigurationView.java:456)
	at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:31)
	at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:94)
	at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:1484)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1327)
	at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1271)
	at org.eclipse.ui.internal.Workbench.run(Workbench.java:1254)
	at
org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:845)
	at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461)
	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:324)
	at org.eclipse.core.launcher.Main.basicRun(Main.java:247)
	at org.eclipse.core.launcher.Main.run(Main.java:703)
	at org.eclipse.core.launcher.Main.main(Main.java:539)

</ Log-File >

This was just a few lines of the .log file there are much more entries based on
the out of memory error.
For further Information, please contact me.

Good Luck finding the error.
Vasudeva
Comment 1 Nick Edgar CLA 2003-03-05 11:08:00 EST
Both stack traces indicate that an attempt to create a new thread failed.
The thread is used to get the features to show in Update's ConfigurationView 
without blocking the UI.  This is new code.  Perhaps these threads are hanging 
around and the system eventually runs out.

If you run eclipse with a console VM (java rather than javaw), you can hit 
Ctrl+Break in the console VM to get a dump of all threads.
The next time this happens, could you please try this and attach the results.
Comment 2 Dejan Glozic CLA 2003-03-05 11:22:07 EST
We dispatch remote connection to a worker thread because in case of a frozen 
connection it can block the UI. Typically, this connection times out eventually 
and the thread exits through the nature death. 

Occasionally, connections block indefinitely. You should check the URL you are 
trying to connect without success. Our connection manager has a limit of 10 
threads before it refuses to create any more. Looks like you hit the 'out of 
memory' state before we hit our limit.

Your main problem is the connection that refuses to time out. If you have such 
a problem, don't try to connect over and over because you will have more 
threads hanging around waiting for time out.

We could kill the threads but according to Java documentation, it is not a safe 
operation and should be avoided. They recommend exactly what we do: allowing 
the thread to exit on its own.
Comment 3 Vasudeva Martin CLA 2003-03-07 05:31:07 EST
I found out, if eclipse freeze in with every new start, it helps if you delete
the ".metadata" directory in your workspace.
But unfortunately all your configuration is lost with this operation. So if you
need, do a backup of the directory before deleting it.
If you haven't configured to much, you can easily import your existing projects,
and resume working.
If somebody wants to do a thread dump on a linux System as described in 
http://bugs.eclipse.org/bugs/show_bug.cgi?id=33836#c1
for german Keyboard you have to press "<Strg>+<Alt Gr>+<ß>".

Here is the thread dump for this bug:

< Thread-Dump >
/usr/local/bin/eclipse: line 5:  1844 Verlassen               $ECLIPSE/eclipse
-vm $JAVA_PATH -data $WORKSPACE -vmargs -Xmx256M
compiler@robotec:~> Full thread dump Java HotSpot(TM) Client VM (1.4.1_01-b01
mixed mode):

"org.eclipse.jface.text.reconciler.Reconciler" daemon prio=1 tid=0x0x83d1b20
nid=0x75d in Object.wait() [bdfff000..bdfff880]
        at java.lang.Object.wait(Native Method)
        - waiting on <0x4586b968> (a
org.eclipse.jface.text.reconciler.DirtyRegionQueue)
        at
org.eclipse.jface.text.reconciler.AbstractReconciler$BackgroundThread.run(AbstractReconciler.java:161)
        - locked <0x4586b968> (a org.eclipse.jface.text.reconciler.DirtyRegionQueue)

"Decoration" prio=1 tid=0x0x820cba8 nid=0x75c in Object.wait() [be1ff000..be1ff880]
        at java.lang.Object.wait(Native Method)
        - waiting on <0x4585efd0> (a
org.eclipse.ui.internal.decorators.DecorationScheduler)
        at java.lang.Object.wait(Object.java:426)
        at
org.eclipse.ui.internal.decorators.DecorationScheduler.next(DecorationScheduler.java:244)
        - locked <0x4585efd0> (a
org.eclipse.ui.internal.decorators.DecorationScheduler)
        at
org.eclipse.ui.internal.decorators.DecorationScheduler$3.run(DecorationScheduler.java:270)
        at java.lang.Thread.run(Thread.java:536)

"org.eclipse.jface.text.reconciler.Reconciler" daemon prio=1 tid=0x0x868e200
nid=0x75b in Object.wait() [be5ff000..be5ff880]
        at java.lang.Object.wait(Native Method)
        - waiting on <0x45835350> (a
org.eclipse.jface.text.reconciler.DirtyRegionQueue)
        at
org.eclipse.jface.text.reconciler.AbstractReconciler$BackgroundThread.run(AbstractReconciler.java:161)
        - locked <0x45835350> (a org.eclipse.jface.text.reconciler.DirtyRegionQueue)

"C Tags indexer" daemon prio=1 tid=0x0x881b718 nid=0x740 in Object.wait()
[be7ff000..be7ff880]
        at java.lang.Object.wait(Native Method)
        - waiting on <0x457b9f30> (a java.util.Collections$SynchronizedList)
        at java.lang.Object.wait(Object.java:426)
        at
org.eclipse.cdt.internal.core.index.RequestList.removeItem(RequestList.java:25)
        - locked <0x457b9f30> (a java.util.Collections$SynchronizedList)
        at org.eclipse.cdt.internal.core.index.CTagsRunner.run(CTagsRunner.java:36)
        at java.lang.Thread.run(Thread.java:536)

"Signal Dispatcher" daemon prio=1 tid=0x0x808d030 nid=0x73c waiting on condition
[0..0]

"Finalizer" daemon prio=1 tid=0x0x80865a0 nid=0x739 in Object.wait()
[bf3ff000..bf3ff880]
        at java.lang.Object.wait(Native Method)
        - waiting on <0x455a7178> (a java.lang.ref.ReferenceQueue$Lock)
        at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:111)
        - locked <0x455a7178> (a java.lang.ref.ReferenceQueue$Lock)
        at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:127)
        at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:159)

"Reference Handler" daemon prio=1 tid=0x0x8085958 nid=0x738 in Object.wait()
[bf5ff000..bf5ff880]
        at java.lang.Object.wait(Native Method)
        - waiting on <0x455a71e0> (a java.lang.ref.Reference$Lock)
        at java.lang.Object.wait(Object.java:426)
        at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:113)
        - locked <0x455a71e0> (a java.lang.ref.Reference$Lock)

"main" prio=1 tid=0x0x8051df0 nid=0x735 runnable [bfffa000..bfffcbf4]
        at org.eclipse.swt.internal.gtk.OS.gtk_main_do_event(Native Method)
        at org.eclipse.swt.widgets.Display.eventProc(Display.java:577)
        at org.eclipse.swt.internal.gtk.OS.gtk_main_iteration(Native Method)
        at org.eclipse.swt.widgets.Canvas.scroll(Canvas.java:169)
        at
org.eclipse.swt.custom.StyledText.setVerticalScrollOffset(StyledText.java:7941)
        at
org.eclipse.swt.custom.StyledText.handleVerticalScroll(StyledText.java:5421)
        at org.eclipse.swt.custom.StyledText$16.handleEvent(StyledText.java:4965)
        at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:77)
        at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:897)
        at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:1507)
        at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1324)
        at org.eclipse.jface.window.Window.runEventLoop(Window.java:577)
        at org.eclipse.jface.window.Window.open(Window.java:557)
        at
org.eclipse.ui.internal.dialogs.MessageDialogWithToggle.openConfirm(MessageDialogWithToggle.java:144)
        at
org.eclipse.ui.internal.WorkbenchWindow.canHandleShellCloseEvent(WorkbenchWindow.java:439)
        at org.eclipse.jface.window.Window$2.shellClosed(Window.java:448)
        at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:152)
        at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:77)
        at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:897)
        at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:922)
        at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:906)
        at org.eclipse.swt.widgets.Shell.closeWidget(Shell.java:424)
        at org.eclipse.swt.widgets.Shell.gtk_delete_event(Shell.java:624)
        at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:1134)
        at org.eclipse.swt.widgets.Display.windowProc(Display.java:1917)
        at org.eclipse.swt.internal.gtk.OS.gtk_main_do_event(Native Method)
        - locked <0x545eadd0> (a java.lang.Class)
        at org.eclipse.swt.widgets.Display.eventProc(Display.java:577)
        at org.eclipse.swt.internal.gtk.OS.gtk_main_iteration(Native Method)
        - locked <0x545eadd0> (a java.lang.Class)
        at org.eclipse.swt.widgets.Canvas.scroll(Canvas.java:169)
        at
org.eclipse.swt.custom.StyledText.setVerticalScrollOffset(StyledText.java:7941)
        at
org.eclipse.swt.custom.StyledText.handleVerticalScroll(StyledText.java:5421)
        at org.eclipse.swt.custom.StyledText$16.handleEvent(StyledText.java:4965)
        at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:77)
        at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:897)
        at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:1507)
        at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1324)
        at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1271)
        at org.eclipse.ui.internal.Workbench.run(Workbench.java:1254)
        at
org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:845)
        at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461)
        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:324)
        at org.eclipse.core.launcher.Main.basicRun(Main.java:247)
        at org.eclipse.core.launcher.Main.run(Main.java:703)
        at org.eclipse.core.launcher.Main.main(Main.java:539)

"VM Thread" prio=1 tid=0x0x8082718 nid=0x737 runnable

"VM Periodic Task Thread" prio=1 tid=0x0x808bb60 nid=0x73a waiting on condition
"Suspend Checker Thread" prio=1 tid=0x0x808c5c8 nid=0x73b runnable
</ Thread-Dump >
 
Comment 4 Dejan Glozic CLA 2003-03-07 09:35:45 EST
There are no Update threads in the last dump. 
Comment 5 Nick Edgar CLA 2003-03-07 10:15:12 EST
Strange that there's a scrollbar event coming in while in the Confirm Exit 
dialog, since it is a modal dialog and has no scrollbars.
Moving to SWT since they're looking at several issues with GTK 2.2.1.
Comment 6 Vasudeva Martin CLA 2003-03-09 17:06:23 EST
The reason why there are no update threads in my thread dump could be that i was
starting eclipse a few times without trying to search for an update. But the
extract of my Log file shows a session where i tried to update eclipse and where
eclipse frozes in a little bit later.
At the Moment I'm using an older Version of eclipse ( M4 ) because ( RC1 )
freezes in even after deleting the .metadata directory in a very short time.
At the moment I noticed, that there is the new Release ( RC2 ). 
I will test it. Maybe the problems are already solved in this version.
Comment 7 Veronika Irvine CLA 2003-03-10 11:50:40 EST
Do you have a repeatable test case for this?

What theme are you using (if any)?
Comment 8 Vasudeva Martin CLA 2003-03-10 12:07:02 EST
Created attachment 3952 [details]
workspace which freezes in Eclipse (RC1) after starting it.

This is my damaged workspace. If you want to see Eclipse freezing in, just
start Eclipse (RC1) with the unpacked attachment as workspace. Move your mouse
to the scroll bar of the opend cpp editor window. Try to scroll the Text.
That's it. On my Computer the text will not scroll and you can't even exit
Eclipse anymore.
Comment 9 Vasudeva Martin CLA 2003-03-10 12:22:58 EST
If you mean GTK-Themes. I think I use no themes. Can't remember that I ever
downloaded or configured somthing like this. The only thing I tried is to change
the Background color of eclipse with System-Colour Settings. But didn't work
although i enabled the checkbox "Apply fonts and colors to non-KDE apps" in the
"style" settings.

In eclipse I changed the "Text Font" Size to 12 point.
("Preferences"->"Workbench"->"Fonts")
Comment 10 Felipe Heidrich CLA 2003-03-11 11:11:03 EST
I think this problem report is a dup of Bug#33652.

Again, the gtk_main_do_event shows up in the stack trace.
I've seen this same function causing problems on Bug#33017 comment 8 and 
Bug#33652 comment 38.
Comment 11 Felipe Heidrich CLA 2003-03-12 14:19:35 EST

*** This bug has been marked as a duplicate of 33652 ***