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

Bug 197789

Summary:	Noticable delay in opening modified bugzilla tasks
Product:	z_Archived	Reporter:	Alex Blewitt <alex.blewitt>
Component:	Mylyn	Assignee:	Mylyn Inbox <mylyn-inbox>
Status:	RESOLVED DUPLICATE	QA Contact:
Severity:	normal
Priority:	P3
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Alex Blewitt

2007-07-25 09:26:03 EDT

When I look in my tasks lists as updated bugs, and double click on them, Eclipse noticably hangs for up to 3s whilst the editor is constructed. It's noticably slower than opening up other editor/file types.

I appreciate that some work will be necessary to populate the editor, and that there may be a task that has to hit the remote repo to get this information, but it shouldn't be invoked in the UI thread. Perhaps it should kick off a background update job, which then opens the editor (and/or updates) with a UI job afterwards?

Comment 1 Eugene Kuleshov

2007-07-25 09:54:50 EDT

In my recollection that delay is caused by the Eclipse forms and the more comments you have, the longer it will take for editor to open. Can you please take some thread dumps during that 3s delay and post or attach the relevant pieces here.

Comment 2 Alex Blewitt

2007-07-25 10:44:27 EDT

I doubt it's the number of comments. This took 1-1.5s to open. And I don't think I can get a breakdown of the threads in that time realistically. I also tried with bug 196082 (5 comments) and this takes about the same amount of time. It could be the fact that we're behind a proxy, but I don't know whether that's the case (or how to view the headers going back and forth). How long does it take you to open this bug?

Comment 3 Alex Blewitt

2007-07-25 10:44:49 EDT

BTW for comparison, it took about 5 seconds to post that last comment.

Comment 4 Eugene Kuleshov

2007-07-25 13:15:33 EDT

I do see difference in time for bugs with 1..5 comments and those with 30 comments... 

Anyways it should be not impossible to do ctrl-tab, ctrl-c within 3s interval. Can you please try that? Another option is to run some script that would force N thread dumps (i.e. using kill -QUIT process_id, or jstack) while you take your time to open the editor.

Comment 5 Steffen Pingel

2009-08-12 22:45:31 EDT


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