Comment 1 Dirk Baeumer 2004-12-22 04:17:32 EST

*** Bug 68895 has been marked as a duplicate of this bug. ***

Comment 2 Dirk Baeumer 2004-12-22 04:22:13 EST

John, does Eclipse really hang at startup. And what perspective are you in when
you shutdown and restart Eclipse ?

Comment 3 Dirk Baeumer 2004-12-22 04:24:46 EST

Pascal, 

can you please shed some light on this. Since I don't know what trigger the
worker-0 thread there is little I can do. Is there any way to find out what job
is actually running in worker thread ?

Comment 4 John Mazzitelli 2004-12-22 08:20:03 EST

Dirk - sorry if I wasn't clear.  When I say "hang at startup", I mean the GUI is
non-responsive for the first X seconds when it starts up (about 5 or 10).  It
"hangs" from the user point of view.  I can't select any menu items, list items
or any GUI components.  The perspectives that it starts up in is either Resource
or Java (I have seen it happen in both).  Once that initial "hang" period, the
GUI becomes responsive again.

So, "hang" was probably a bad word, since the problem isn't permanent.  Its a
temporary condition that only occurs during the first few seconds during startup.

Comment 5 Dirk Baeumer 2004-12-22 09:54:22 EST

OK will adjust title than.

Comment 6 Dirk Baeumer 2005-01-04 13:14:58 EST

Pascal, can you please comment !

Comment 7 Pascal Rapicault 2005-01-04 16:28:39 EST

I'm back from vacation!
There is no way to know what is triggering the thread "worker-0" nor what it is 
doing except that it is starting the jdt.ui plugin.
The only thing I can say from that is that jdt.ui is taking a long time to 
start.

Comment 8 Pascal Rapicault 2005-01-04 16:44:16 EST

Now that I'm fully awake, you can know who and why jdt ui is being activated by
using the core tools.

Comment 9 Dirk Baeumer 2005-01-05 05:33:40 EST

John,

is it possible that you create a VM dump the next time you are seeing the hang.
This would allow to understand what is going on in the worker thread. 

I am not seeing the hand on my machine.

Comment 10 John Mazzitelli 2005-01-05 09:37:14 EST

Unfortunately, I cannot replicate this so easily anymore (I just tried 5 or 6
times right now, going to different workspaces, and didn't see it).

After I reported this, I removed some plugins that I didn't use much, and now I
don't see this as often (I did see it a few days ago, but its now a rare occurence).

When I see it again, I'll be sure to take a dump and post it here.

Comment 11 Dirk Baeumer 2005-01-05 09:55:13 EST

Thanks John.

Comment 12 Guillaume Outters 2005-01-22 16:00:22 EST

If this can help, I've got the same symptoms with:
- JDK 1.4.2_05
- eclipse-SDK-N20050120-0010-macosx-carbon
- PHPEclipse1.1.2-2004-12-04

Sometimes (about one in three startups, with no particular pattern), when firing up Eclipse, each one of 
400 classes of PHPEclipse timeouts with 5 s (I let it do that entirely once, and, yes, I then have the 
functionnal environment).

I went into jdb, and found Worker-0 waiting for a lock. But doing a "lock work" got me a "Operation is 
not supported on the target VM".

OK, here are my threads:
  (java.lang.Thread)0x1                                               main                         cond. waiting
  (org.eclipse.osgi.framework.eventmgr.EventThread)0xa10              Framework Event Dispatcher   
cond. waiting
  (org.eclipse.osgi.framework.eventmgr.EventThread)0xa11              Start Level Event Dispatcher cond. 
waiting
  (org.eclipse.core.internal.jobs.Worker)0xa12                        Worker-0                     running
  (org.eclipse.jface.resource.ImageCache$ReferenceCleanerThread)0xa13 Reference Cleaner: 1         
cond. waiting

Here's what Worker-0 is doing, well, waiting for:
  [1] java.lang.Object.wait (native method)
  [2] org.eclipse.ui.internal.Semaphore.acquire (Semaphore.java:41)
  [3] org.eclipse.ui.internal.UISynchronizer.syncExec (UISynchronizer.java:45)
  [4] org.eclipse.swt.widgets.Display.syncExec (Display.java:3?335)
  [5] net.sourceforge.phpdt.ui.PreferenceConstants.initializeDefaultValues (PreferenceConstants.java:2?
249)
  [6] net.sourceforge.phpeclipse.PHPeclipsePlugin.initializeDefaultPreferences (PHPeclipsePlugin.java:
843)
  [7] org.eclipse.ui.plugin.AbstractUIPlugin.initializeDefaultPluginPreferences (AbstractUIPlugin.java:354)
  [8] org.eclipse.core.runtime.Plugin.internalInitializeDefaultPluginPreferences (Plugin.java:408)
  [9] org.eclipse.core.internal.preferences.DefaultPreferences.applyRuntimeDefaults 
(DefaultPreferences.java:204)
  [10] org.eclipse.core.internal.preferences.DefaultPreferences.loadDefaults (DefaultPreferences.java:
301)
  [11] org.eclipse.core.internal.preferences.DefaultPreferences.load (DefaultPreferences.java:297)
  [12] org.eclipse.core.internal.preferences.EclipsePreferences.create (EclipsePreferences.java:298)
  [13] org.eclipse.core.internal.preferences.EclipsePreferences.internalNode (EclipsePreferences.java:
531)
  [14] org.eclipse.core.internal.preferences.EclipsePreferences.node (EclipsePreferences.java:660)
  [15] org.eclipse.core.internal.preferences.AbstractScope.getNode (AbstractScope.java:39)
  [16] org.eclipse.ui.preferences.ScopedPreferenceStore.getDefaultPreferences 
(ScopedPreferenceStore.java:226)
  [17] org.eclipse.ui.preferences.ScopedPreferenceStore.getPreferenceNodes 
(ScopedPreferenceStore.java:257)
  [18] org.eclipse.ui.preferences.ScopedPreferenceStore.contains (ScopedPreferenceStore.java:314)
  [19] net.sourceforge.phpeclipse.PHPeclipsePlugin.installPreferenceStoreBackwardsCompatibility 
(PHPeclipsePlugin.java:1?084)
  [20] net.sourceforge.phpeclipse.PHPeclipsePlugin.start (PHPeclipsePlugin.java:1?224)
  [21] org.eclipse.core.internal.compatibility.PluginActivator.start (PluginActivator.java:30)
  [22] org.eclipse.osgi.framework.internal.core.BundleContextImpl$2.run (BundleContextImpl.java:989)
  [23] java.security.AccessController.doPrivileged (native method)
  [24] org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator 
(BundleContextImpl.java:985)
  [25] org.eclipse.osgi.framework.internal.core.BundleContextImpl.start (BundleContextImpl.java:968)
  [26] org.eclipse.osgi.framework.internal.core.BundleHost.startWorker (BundleHost.java:311)
  [27] org.eclipse.osgi.framework.internal.core.AbstractBundle.start (AbstractBundle.java:274)
  [28] org.eclipse.core.runtime.adaptor.EclipseClassLoader.findLocalClass (EclipseClassLoader.java:110)
  [29] org.eclipse.osgi.framework.internal.core.BundleLoader.findLocalClass (BundleLoader.java:332)
  [30] org.eclipse.osgi.framework.internal.core.BundleLoader.findClass (BundleLoader.java:358)
  [31] org.eclipse.osgi.framework.adaptor.core.AbstractClassLoader.loadClass 
(AbstractClassLoader.java:94)
  [32] java.lang.ClassLoader.loadClass (ClassLoader.java:235)
  [33] org.eclipse.osgi.framework.internal.core.BundleLoader.loadClass (BundleLoader.java:272)
  [34] org.eclipse.osgi.framework.internal.core.BundleHost.loadClass (BundleHost.java:222)
  [35] org.eclipse.osgi.framework.internal.core.AbstractBundle.loadClass (AbstractBundle.java:1?213)
  [36] org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension 
(ConfigurationElement.java:161)
  [37] org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension 
(ConfigurationElement.java:151)
  [38] org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension 
(ConfigurationElement.java:138)
  [39] org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension 
(ConfigurationElementHandle.java:48)
  [40] org.eclipse.core.internal.events.BuildManager.instantiateBuilder (BuildManager.java:718)
  [41] org.eclipse.core.internal.events.BuildManager.initializeBuilder (BuildManager.java:670)
  [42] org.eclipse.core.internal.events.BuildManager.getBuilder (BuildManager.java:429)
  [43] org.eclipse.core.internal.events.BuildManager.basicBuild (BuildManager.java:195)
  [44] org.eclipse.core.internal.events.BuildManager$1.run (BuildManager.java:226)
  [45] org.eclipse.core.internal.runtime.InternalPlatform.run (InternalPlatform.java:1?071)
  [46] org.eclipse.core.runtime.Platform.run (Platform.java:747)
  [47] org.eclipse.core.internal.events.BuildManager.basicBuild (BuildManager.java:229)
  [48] org.eclipse.core.internal.events.BuildManager.basicBuildLoop (BuildManager.java:248)
  [49] org.eclipse.core.internal.events.BuildManager.build (BuildManager.java:277)
  [50] org.eclipse.core.internal.events.AutoBuildJob.doBuild (AutoBuildJob.java:141)
  [51] org.eclipse.core.internal.events.AutoBuildJob.run (AutoBuildJob.java:202)
  [52] org.eclipse.core.internal.jobs.Worker.run (Worker.java:66)

Comment 13 Guillaume Outters 2005-01-22 16:06:02 EST

Could this bug get changed to Platform: All, OS: All, Version: 3.1?

Comment 14 Dirk Baeumer 2005-01-23 11:58:26 EST

Guillaune,

you problem isn't caused by JDT/UI. It is cause bay the PHPPlugin itself. What
the do in the start method of their plug-in is a sync exec into the UI thread.
This definitelly asks for trouble.

Can you please report the bug in the corresponding Bug system of the PHP plugin.
There is nothing Eclipse can do here.

Comment 15 Dirk Baeumer 2005-01-23 11:59:55 EST

John,

I will set the PR to remind until you can reproduce the problem.

Comment 16 Pascal Rapicault 2005-01-24 08:46:20 EST

Guillaume, it might be good to open a bug report against the owner of the PHP
plugin, because what they are doing is bad practice.

Comment 17 John Mazzitelli 2005-01-24 09:42:27 EST

I just got it to happen again this morning (side note: I had killed Eclipse
abnormally on Friday via Windows TaskManager which reset my workspace - I now
got it to happen again - have no idea if that is significant or not; thought i
should bring it up though).

I will attach my thread dump.  Sorry for the formatting, had to cut-n-paste from
command window - how do you get thread dumps (via Ctrl-Break) to show up in
.log?  All I got was the exception stack trace in .log, but nothing from
Ctrl-Break).  In any event, I think it will be helpful.

Comment 18 John Mazzitelli 2005-01-24 09:44:46 EST

Created attachment 17390 [details]
thread dump during the "hang"

This is the thread dump of the Eclipse JVM during the startup "hang".  I will
leave it up to this issue's owner to consider reopening this issue, assuming
this thread dump provides enough information to continue investigation.

Comment 19 Dirk Baeumer 2005-01-25 10:02:12 EST

Created attachment 17424 [details]
Formatted thread dump

Comment 20 Dirk Baeumer 2005-01-25 10:06:46 EST

Pascal,

can you please have a look at the thread dump attached under comment #19.

What I don't understand is the fact that main is waiting on a lock in
EclipseClassLoader.findLocalClass (some lock for bundle state changes). However,
the JavaPlugin must already be loaded and initialized since code prior to that
call in main is code from JDT/UI
(org.eclipse.jdt.internal.corext.util.AllTypesCache).

The Worker-0 thread seems to wait on the JavaPlugin as well.

We want to get rid of the all types cache for 3.1. However, I would like to
understand what's going on here to avoid such situations in the future.

Comment 21 Dirk Baeumer 2005-02-10 13:47:59 EST

Pinging Pascal...

Comment 22 Pascal Rapicault 2005-03-11 17:06:43 EST

I looked at the trace several times but could not reach a conclusion.
Sorry.

Comment 23 Pascal Rapicault 2005-03-11 17:07:06 EST

Sorry I did not mean to close it.

Comment 24 Dirk Baeumer 2005-03-14 06:36:23 EST

Pascal, any form of speculation. As said all that happens in core runtime and I
don't see what JDT/UI can do here.

Comment 25 Dirk Baeumer 2005-03-14 06:36:45 EST

John, have you seen such hangs in the past ?

Comment 26 John Mazzitelli 2005-03-14 09:20:11 EST

I can't remember when I started seeing this - I am almost positive I started
seeing this in the 3.0.1 version.  I've been using 3.1 M4 and now M5 for a
while, and while I do see this problem, it doesn't seem to be as prevalent as
before. Either the M's are getting more stable as you go along :-) or something
else is happening in the way I am using the tool that circumvents the problem
(what that is I dunno).  For me personally, this problem isn't as serious as
when I first reported it.  Before, I was getting this everytime I started
Eclipse, now I rarely see it.  It may have to do with the number of projects in
my workspace, but then again, I thought that before and I remember seeing the
problem with only a single project.  So, I'm baffled.

Comment 27 Denis Roy 2009-08-30 02:07:07 EDT

As of now 'LATER' and 'REMIND' resolutions are no longer supported.
Please reopen this bug if it is still valid for you.