| Eclipse hangs while launching run-time workbench [message #274994] |
Tue, 02 November 2004 14:25  |
Eclipse User |
|
|
|
Originally posted by: jojo.virtutech.se
Hi!
I've got a plugin-project which I'm testing by starting a run-time
workbench. Most of the time, this works fine, but every once in a while the
run-time workbench never starts. I get a splash-screen, then nothing
happens. Eventually the workbench starts, but after several minutes of
waiting.
The host machine runs Gentoo Linux, the Eclipse version is 3.0.1.
The run-time workbench does not consume any CPU; the Eclipse process is in
a waiting poll() call and the Java process is in a poll() loop.
Anybody recognize this behavior?
I realize this isn't a very good bugreport, but I'm all out of
ideas. Waiting 2-3 minutes every time I want to start a run-time workbench
isn't very fun. The 10-15 seconds it usually takes is bad enough.
--
/Jesper
|
|
|
| Re: Eclipse hangs while launching run-time workbench [message #274998 is a reply to message #274994] |
Tue, 02 November 2004 15:03  |
| Eclipse User |
|
|
|
Originally posted by: bbiggs.ca.ibm.com
Jesper Eskilson wrote:
> I've got a plugin-project which I'm testing by starting a run-time
> workbench. Most of the time, this works fine, but every once in a while the
> run-time workbench never starts. I get a splash-screen, then nothing
> happens. Eventually the workbench starts, but after several minutes of
> waiting.
>
> The host machine runs Gentoo Linux, the Eclipse version is 3.0.1.
>
> The run-time workbench does not consume any CPU; the Eclipse process is in
> a waiting poll() call and the Java process is in a poll() loop.
>
> Anybody recognize this behavior?
>
> I realize this isn't a very good bugreport, but I'm all out of
> ideas. Waiting 2-3 minutes every time I want to start a run-time workbench
> isn't very fun. The 10-15 seconds it usually takes is bad enough.
You should get a stack trace from Eclipse and see where it is hung. I
think you might be seeing something like this:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=74498
Basically, if some application owns the clipboard and is unresponsive,
Eclipse can hang waiting for the clipboard contents. The timeout for
clipboard contents in GTK+ is 5 minutes.
If it's only hanging for 2-3 minutes this might not be the problem
though. You should probably file a bug report with a stack trace (you
can get one by sending the java process a kill -3).
-Billy
|
|
|
|
Powered by
FUDForum. Page generated in 0.03842 seconds
] 
Search
Help
Register
Login
Home
