Community
Participate
Working Groups
Build ID: M20070212-1330 Steps To Reproduce: 1.Create a workspace on Linux (64-bit OS and 32-bit JDK) with multi-level directory path and each directory path may contains hundreds of files 2.Click on File -> Switch Workspace -> Browse 3.It will take 3-4 minutes for the browse to come up More information: With the same Eclipse level on Windows XP, the switch workspace problem does not occur.
Hi. Any possibility of this being fixed?
Do you still get the same delay when you do a File -> Open File... ?
There is an IBM RATLC defect 394671 opened to track this issue.
Are you saying that this bug report can be closed because this has been identified as an IBM product issue?
Sorry for the confusion. This problem report should remain open because this problem is not an IBM product issue. Thanks.
Since the delay occurs in opening the directory selection dialog, this doesn't seem to have anything to do with runtime. Moving back to UI.
It would be very useful to have an idea what is going on during those 3-4 minutes. A few stack dumps taken during that delay would likely pinpoint the problem. See this wiki page for info on how to generate stack dumps: http://wiki.eclipse.org/index.php/How_to_report_a_deadlock
Your instructions are somewhat ambiguous as well. There is no File-Switch Workspace-Browse option, but there is a File-Switch Worspace-Other option that opens a dialog containing a Browse button which does open a dialog as well. Which of these dialogs is taking a long time?
Hundreds of the following messages were returned when user waiting for eclipse workspace to switch on Linux 64-bit. There is no exceptions returned. stat64(0x7ca964d0, 0x7cacca88) = 0 stat64(0x7ca964d0, 0x7cb20e98) = 0 stat64(0x7ca964d0, 0x7cb110f8) = 0 stat64(0x7ca964d0, 0x7ca8d6a8) = 0 stat64(0x7ca964d0, 0x7cb2a368) = 0 stat64(0x7cae9c38, 0x7caa9e08) = 0 stat64(0x7ca964d0, 0x7cb29068) = 0 stat64(0x7ca964d0, 0x7caf3e68) = 0 stat64(0x7ca964d0, 0x7caf4ce8) = 0 The wait appears when the file browse action button is pressed.
Does this delay also happen on startup if you choose the browse option from the workbench chooser dialog?
You specify that you're using a 32-bit jdk, so presumably a 32-bit eclipse as well. Do you see the same problem if you run with 64-bit eclipse and 64-bit jre? And does it only happen if you have a "multi-level directory path and each directory path may contains hundreds of files"?
Pinging those who reported the bug for more input.
Wu: please reopen if you can provide the requested information.
Sorry for not responding sooner. This problem occurs on Linux 64-bit system where there are hundreds of entries in each directory with typically 5-10 level deep directory hierachy. These directories reside on AFS or network shared drive, which are not local to where the eclipse workspace is.
Wu, please see comment #7. If you could give one or two stack dumps during that 3-4 minute delay, it would greatly help tracking down what is happening and where the time is going.
(In reply to comment #14) > Sorry for not responding sooner. This problem occurs on Linux 64-bit system > where there are hundreds of entries in each directory with typically 5-10 level > deep directory hierachy. These directories reside on AFS or network shared > drive, which are not local to where the eclipse workspace is. > Also, answering Grants question about the 64 bit eclipse/vm would be helpful as well.
The application that Wu is talking about can only run on eclipse 3.2.2. and 32 bit. So, will not be able to test with 64bit JDK.
The "Browse" button on the File -> Switch Workspace... -> Other dialog opens org.eclipse.swt.widgets.DirectoryDialog. Assuming that this is the dialog Wu is referring to, reassigning to SWT. Wu, it would help if you could provide more information as asked in: comment 8 - is this the dialog you having the problem with? comment 7, comment 15 - can you provide some stack traces to see what happens in the 3-4 minutes of waiting? comment 2 - do you see a similar slowdown in the File -> Open File on the same directory?
What Linux are you running ? Is the path on a network drive ? Have you tried with a new version of Eclipse (ie. Eclipse 3.5 M6) ?
This looks like a bug in GTK. The GTK file dialog seems to be doing a hundreds of stat64()'s in an attempt to fill the dialog. This is not SWT.
Changed to NOT_ECLIPSE, since it's not an Eclipse bug.
