Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 357070 - Eclipse hangs at "initializing java tooling"
Summary: Eclipse hangs at "initializing java tooling"
Status: RESOLVED WONTFIX
Alias: None
Product: JSDT
Classification: WebTools
Component: General (show other bugs)
Version: 3.3   Edit
Hardware: PC Windows XP
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact: Nitin Dahyabhai CLA
URL:
Whiteboard:
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2011-09-08 08:23 EDT by razvan CLA
Modified: 2013-06-18 10:57 EDT (History)
5 users (show)

See Also:

Attachments
Thread dump (29.29 KB, application/octet-stream)
2011-09-08 09:52 EDT, razvan CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description razvan CLA 2011-09-08 08:23:18 EDT 
Build Identifier:  20110615-0604

I am using the latest release of Eclipse Indigo and I get the same problem as in bug 241343. Practically the Eclipse becomes unusable and it states: Initializing Java Tooling (1%) and it never ends. This is a huge problem because I can not use the IDE unless I change my workspace. This bug should have been solved because it is an older issue as far as I've seen on the internet. 

Reproducible: Always

Steps to Reproduce:
see bug 241343
Comment 1 Remy Suen CLA 2011-09-08 08:29:23 EDT 
Please get a thread dump from Visual VM.
http://wiki.eclipse.org/index.php/How_to_report_a_deadlock
Comment 2 razvan CLA 2011-09-08 09:52:00 EDT 
Created attachment 202989 [details]
Thread dump
Comment 3 razvan CLA 2011-09-08 09:53:49 EDT 
(In reply to comment #1)
> Please get a thread dump from Visual VM.
> http://wiki.eclipse.org/index.php/How_to_report_a_deadlock

Hi,
  
  I used JVM to get the thread dump. Please take a look to see if it makes a difference.

Thanks!
Razvan
Comment 4 Olivier Thomann CLA 2011-09-08 09:55:45 EDT 
Jay, please take a look.
Comment 5 Jay Arthanareeswaran CLA 2011-09-08 09:56:31 EDT 
Looks like a JSDT problem to me.
Comment 6 Nitin Dahyabhai CLA 2011-09-12 15:43:26 EDT 
(In reply to comment #5)
> Looks like a JSDT problem to me.

I highly doubt that.  Looks like we're waiting for access to the workspace, just like everyone else but Worker-0, who's performing a refresh.

Was Eclipse started with the -refresh argument?
Comment 7 razvan CLA 2011-09-13 02:25:31 EDT 
(In reply to comment #6)
> (In reply to comment #5)
> > Looks like a JSDT problem to me.
> 
> I highly doubt that.  Looks like we're waiting for access to the workspace,
> just like everyone else but Worker-0, who's performing a refresh.
> 
> Was Eclipse started with the -refresh argument?

No, I simply started it by click-ing the executable in explorer.
Comment 8 Chris Jaun CLA 2013-06-18 10:57:39 EDT 
I don't see any indication that this is a JSDT issue in the thread dump. Being that this bug is over 20 months old, I am closing it.