Bug 8821 - Opening editors has become very slow
Summary: Opening editors has become very slow
Status: RESOLVED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 2.0   Edit
Hardware: Other Linux-Motif
: P1 major (vote)
Target Milestone: ---   Edit
Assignee: Carolyn MacLeod CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-01-31 08:41 EST by Jared Burns CLA
Modified: 2018-03-13 14:40 EDT (History)
5 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jared Burns CLA 2002-01-31 08:41:21 EST
Build 20020129 (and possibly 0125)

Opening editors has become extremely slow on Linux motif.

1. Double click on a file in the navigator view
2. Wait approx. 8 seconds for the editor to open

It used to take approx. 1 second to open an editor.
Comment 1 Mike Wilson CLA 2002-01-31 14:52:39 EST
Not all platform-specific performance problems are SWT related. In this case, 
there could be several issues related to the relative performance of file 
systems, for example, which could be causing the problem.

Moving to UI to do the initial investigation.
Comment 2 Jared Burns CLA 2002-02-12 16:29:33 EST
I double checked and this bug does not exist in the 20020125 build. It was
introduced in 20020129.
Comment 3 Kevin Haaland CLA 2002-02-13 09:12:05 EST
Getting the list of avaiable printers on Linux is very slow. Pls take a look at 
Printer.getPrinterList()

Commenting out this code significantly improves the time to open editors. 
Comment 4 Mike Wilson CLA 2002-02-13 11:53:31 EST
Oddly enough, this operation takes approx 1ms on all machines we test on. 
However, I have seen it happen on KH's machine, and it has been reported by 
several others now.

CM is investigating. Current theory is that it is related to whether or not 
printing support is installed. We plan to modify the code to cache the return 
value after the first call. Note that this will imply that you will need to 
exit and restart eclipse in order to detect when a printer is installed.
Comment 5 Jared Burns CLA 2002-02-13 12:14:40 EST
Opened Bug 9692. I have a printer installed, but Eclipse fails to recognize it.
Comment 6 Carolyn MacLeod CLA 2002-02-13 14:32:56 EST
Due to unbelievable IDE problems, I am unable to debug a good patch in real 
time. So I am forced to release a patch now that disables Linux printing 
altogether. This "disable printing" code is now released in the current stream.

On my machine and 2 others, XtOpenDisplay takes only 1ms if there is no Xprt 
server running on screen :1, and it takes only 100ms (slow, but not anywhere 
near 7 seconds) if the Xprt server is running fine.

I strongly suspect that there is some configuration/setup problem on the 
machines that are running slowly, and I suspect that any call to XtOpenDisplay 
or XOpenDisplay will take a long time.

I will try to find a good work-around as soon as I can, but for now we felt it 
was best to just get something out there that works so that the build can go on.
Comment 7 John Wiegand CLA 2002-05-30 20:27:25 EDT
This defect should be closed - we are not encountering this problem any longer.
Comment 8 Carolyn MacLeod CLA 2002-05-30 22:22:01 EDT
Agree - closing.
Comment 9 Felipe Heidrich CLA 2002-09-19 13:41:06 EDT
Printing on Linux/Motif was reactivated.

If you don't have Xprint configured in your system methods like 
Printer.getPrinterList() should return a empty list in 50 millisecond or so 
since no Xdisplay is going to be open.

Please, let me know if you restart having problems with Printing on Motif.



Comment 10 Veronika Irvine CLA 2005-03-17 16:08:45 EST
*** Bug 85438 has been marked as a duplicate of this bug. ***