|
| Re: Potential deadlock when initializing Java tooling [message #991452 is a reply to message #991413] |
Wed, 19 December 2012 03:53  |
Eclipse User |
|
|
|
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!
|
|
|
Powered by
FUDForum. Page generated in 0.03444 seconds
Home
