Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Language IDEs » Java Development Tools (JDT) » Potential deadlock when initializing Java tooling
Potential deadlock when initializing Java tooling [message #991413] Wed, 19 December 2012 00:24 Go to next message
Mirko Raner is currently offline Mirko Raner
Messages: 79
Registered: July 2009
Location: San Diego, CA
Member
Hi there,

I just upgraded my Android SDK for a Juno SR1 instance running on a very large workspace, and upon starting Eclipse is non-responsive for a long time. I can't interact with the workbench (Windows says "Not responding...") but the progress view shows this:

index.php/fa/12741/0/

It looks like it's doing a workspace build before the JDT tooling is fully initialized. The workspace has about 50 dependent projects, most of which are Java and/or Android projects.
Could this be some deadlock? Would Java tooling have to be fully initialized before the workspace can even build?
Eclipse eventually recovered, but it was stuck in this state for at least 10 minutes.
I can't reliably reproduce this, but is there anything else I could try to shed more light on this problem?

Thanks!
  • Attachment: Deadlock.png
    (Size: 17.52KB, Downloaded 206 times)
Re: Potential deadlock when initializing Java tooling [message #991452 is a reply to message #991413] Wed, 19 December 2012 08:53 Go to previous message
Dani Megert is currently offline Dani Megert
Messages: 3801
Registered: July 2009
Senior Member
On 19.12.2012 01:24, Mirko Raner wrote:
> Hi there,
>
> I just upgraded my Android SDK for a Juno SR1 instance running on a very large workspace, and upon starting Eclipse is non-responsive for a long time. I can't interact with the workbench (Windows says "Not responding...") but the progress view shows this:
>
>
>
> It looks like it's doing a workspace build before the JDT tooling is fully initialized. The workspace has about 50 dependent projects, most of which are Java and/or Android projects.
> Could this be some deadlock? Would Java tooling have to be fully initialized before the workspace can even build?
> Eclipse eventually recovered, but it was stuck in this state for at least 10 minutes.
> I can't reliably reproduce this, but is there anything else I could try to shed more light on this problem?
Make some stack traces and report the bug against Android tooling.

Dani
>
> Thanks!
Previous Topic:Eclipse Ant and cvs problem
Next Topic:SSCCE Project Setup...
Goto Forum:
  


Current Time: Wed Oct 01 04:08:15 GMT 2014

Powered by FUDForum. Page generated in 0.13357 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software