Eclipse Community Forums: Java Development Tools (JDT) » Potential deadlock when initializing Java tooling

Help

Home

Home » Language IDEs » Java Development Tools (JDT) » Potential deadlock when initializing Java tooling

Show: Today's Messages :: Show Polls :: Message Navigator

Potential deadlock when initializing Java tooling [message #991413]

Wed, 19 December 2012 00:24

Mirko Raner

Messages: 125
Registered: July 2009
Location: New York City, NY

Senior 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 479 times)

Report message to a moderator

Re: Potential deadlock when initializing Java tooling [message #991452 is a reply to message #991413]

Wed, 19 December 2012 08:53

Dani Megert

Messages: 3802
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!

Report message to a moderator

Previous Topic:	Eclipse Ant and cvs problem
Next Topic:	SSCCE Project Setup...

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Thu Apr 25 20:32:48 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter