Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 364685

Summary:	EGIT synchronization makes Eclipse really really slow
Product:	[Technology] EGit	Reporter:	Ed Willink <ed>
Component:	Core	Assignee:	Project Inbox <egit.core-inbox>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	critical
Priority:	P3	CC:	remy.suen
Version:	1.1
Target Milestone:	---
Hardware:	PC
OS:	Windows Vista
Whiteboard:

Description Ed Willink

2011-11-24 03:44:50 EST

(3.8M3) with many moduling projects, CVS, SVN

Prior to Synchronize Workspace, my Eclipse 3.8M3 is not spectacularly fast but it is useable.

After a Synchronize Workspace things can get really slow.

For instance setting a breakpoint while in the debugger seems to provide a workspace hbu8old that provokes GIT synchronize.

Relaunching a JUnit test after changing just a breakpoint has finally driven me to distraction. Adter two minutes I just closed Eclipse and started again.

There is some really bad interaction between EGIT Synchronize and other aspects of Eclipse, particularly builders.

I'm pretty sure that EGIT triggers a build after each open/import project, so a multi-project import creates a cascade of concurrent builds that make take many minutes to stabilize. I usually disable auto-build so that it only takes a minute.

Comment 1 Remy Suen

2011-11-24 14:13:04 EST

What build of EGit are you using?

Comment 2 Ed Willink

2011-11-24 14:25:53 EST

(In reply to comment #1)
> What build of EGit are you using?

1.1 seemed to be all that was available from staging, and you don't seem to provide a better repo on your downloads page.

Comment 3 Remy Suen

2011-11-24 14:29:43 EST

(In reply to comment #2)
> (In reply to comment #1)
> > What build of EGit are you using?
> 
> 1.1 seemed to be all that was available from staging, and you don't seem to
> provide a better repo on your downloads page.

Thanks for your information. Wanted to check if you were using the nightlies or not.

Dariusz and I worked together on some improvements while looking at bug 358898. If nothing else, the breakpoint problem should be gone.

Comment 4 Ed Willink

2011-11-24 14:40:23 EST

Seems like there's enough familiar symptoms in Bug 358898 to mark this as a duplicate.

Comment 5 Remy Suen

2011-11-24 14:43:57 EST

(In reply to comment #4)
> Seems like there's enough familiar symptoms in Bug 358898 to mark this as a
> duplicate.

Thanks Edward. If you still notice problems with the nightly, please do not hesitate to reopen the bug and attach a thread dump.
http://wiki.eclipse.org/index.php/How_to_report_a_deadlock

*** This bug has been marked as a duplicate of bug 358898 ***

Comment 6 Ed Willink

2011-11-24 15:39:38 EST

Where are the nightlies?

http://www.eclipse.org/projects/project.php?id=technology.egit contains a "Downloads" link that 404's.

The listed update site repo has nothing more recent that 15-September.

Comment 7 Paul Webster

2011-11-24 15:42:37 EST

http://download.eclipse.org/egit/updates-nightly is the one I use
PW

Comment 8 Ed Willink

2011-11-25 10:00:28 EST

(In reply to comment #5)
> If you still notice problems with the nightly.

Wow! It's magic, suddenly Eclipse is useable again.

Still an NPE pop-up before and after many commits, but it seems benign.

Comment 9 Remy Suen

2011-11-25 13:54:41 EST

(In reply to comment #8)
> Still an NPE pop-up before and after many commits, but it seems benign.

Please open a bug for this problem, Edward.

Comment 10 Ed Willink

2011-11-27 10:10:13 EST

(In reply to comment #9)
> (In reply to comment #8)
> > Still an NPE pop-up before and after many commits, but it seems benign.
> 
> Please open a bug for this problem, Edward.

Bug 364909 might be it.