[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[news.eclipse.tools] Re: Workbench shutdown does not complete
Normal bug spin up/down of the workbench works fine - terminates as expected.
If help has been started, even if the perspective has been closed, termination hangs.

After help has been started I see the HelpServer thread - it stays after the perspective has been closed.

When I ask for help content I can see connection threads flashing in the debug view.

I end up with five threads in the debug view:

Four have stacks:
System Thread [Finalizer] (Suspended)
 Object.wait(long)
 ReferenceQueue.remove(long) line: 114
 ReferenceQueue.remove() line: 129
 Finalizer$FinalizerThread.run() line: 168

System Thread [Reference Handler] (Suspended)
 Object.wait(long)
 Reference$Lock(Object).wait() line: 421
 Reference$ReferenceHandler.run() line: 116
 

Thread [main] (Suspended)
 PlainSocketImpl.socketClose()
 PlainSocketImpl.close() line: 478
 ServerSocket.close() line: 280
 HelpServer.close() line: 58
 HelpSystem.shutdown() line: 253
 WorkbenchHelpPlugin.shutdown() line: 80
 PluginRegistry$2.run() line: 257
 InternalPlatform.run(ISafeRunnable) line: 758
 PluginRegistry$1.visit(IPluginDescriptor) line: 266
 PluginRegistry.accept(IPluginVisitor, boolean) line: 45
 PluginRegistry.shutdownPlugins() line: 269
 PluginRegistry.shutdown(IProgressMonitor) line: 244
 InternalPlatform.loaderShutdown() line: 472
 Method.invoke(Object, Object[])
 InternalBootLoader.shutdown() line: 888
 InternalBootLoader.run(String, URL, String, String[]) line: 820
 BootLoader.run(String, URL, String, String[]) line: 285
 Method.invoke(Object, Object[])
 UIMain(Main).basicRun(String[]) line: 119
 UIMain(Main).run(String[]) line: 401
 UIMain.main(String[]) line: 52
 

Thread [HelpServer] (Suspended)
 PlainSocketImpl.socketAccept(SocketImpl)
 PlainSocketImpl.accept(SocketImpl) line: 430
 ServerSocket.implAccept(Socket) line: 255
 ServerSocket.accept() line: 234
 HelpServer.run() line: 130

Is it the socket bit between main and the HelpServer?

I understand that the help server runs on localhost - are there any special settings/issues with tcp/ip configs?  When I ping localhost I get a 127.0.0.1 response, but it also tells me my host name is CORK, which is my defined hostname for the machine.  I'd have to check if this happens on other machines were shutdown is not a problem.

Pat Mc.
 

Jeff McAffer wrote:

Pat,

Stumped on this one.  Since you can get it to happen when running in debug
mode, perhaps you could pause the remaining threads and see what is
happening.  To do this, run the "target" Eclipse as you described (using the
debugger <aka 'the bug'>).  When you exit the target and it is left running,
select the remaining threads and use the debugger's pause button and review
the stacks.  Chances are that most of the threads are random things like
indexers or reconcilers etc. that don't cause much trouble. Look for threads
with "main" or "modal" in their name or with non-trivial stacks and some
sort of blocking call (semaphore acquisition, wait(), ...) at the top.  In
this case you might also look for "help" related threads.

Check this out and let us know what you find.  Its very curious...

Thanks

Jeff

"Pat McCarthy" <patmc@xxxxxxxxxx> wrote in message
news:3B4DC706.7FEC9CEA@xxxxxxxxxx...
> I'm having an intermittent problem during the shutdown of the workbench.
>
> The UI goes away and I can start the workbench again without trouble,
> but the first javaw.exe is still running in the background (not doing
> much).  I can get four or five of these hanging javaw.exe processes left
> running and consuming virtual memory.
>
> I thought I was alone with this problem as I could not get others to
> mimic my results on their machine.   I've now found several others that
> do have this problem but have not found anything consistent in the
> config that would help identify why this occurs.
>
> We do know that it seems to happen when the help perspective has been
> used/is left up when we shutdown.  If I close the help perspective and
> go through a shutdown/restart/shutdown cycle - the process is closed
> after the second shutdown (but the process from the first shutdown is
> still there).
>
> I've got IE 5.00.3103.nnnn installed.  It does not happen on a
> team-mates machine (he has IE 5.50.4134.nnn), but it does happen on
> another machine where IE is at 5.50.42nn.nnnn.  So there does not seem
> to be a relationship between the IE level and the hanging javaw.exe
> processes.
>
> I can get the same behavior if I start the workbench (run or debug) from
> a plugin in the PDE.  The task stays in the debug window after the
> launched workbench is shutdown (but closes nicely if I close the help
> perspective and shutdown/restart/shutdown).
>
> Is there a startup option I can use to find out why the javaw.exe
> process hangs?
>
> Thanks,
>     Pat Mc.
>