Community
Participate
Working Groups
Greetings, I am running Eclipse 3.0.2 on Ubuntu "Hoary". Kernel 2.6.10-5. I have Eclipse placed in /usr/local/eclipse. I am launching the application from a desktop launcher. When the splash screen appears it prompts for a workspace location. The following scenarios have been experienced: - workspace is on an NFS share causes the startup to hang indefinately. - workspace is a link to a workspace directory on an NFS share causes the startup to hang indefinately. - workspace on the local disk works properly. I realize this is pretty insignificant, but the app is so useful I thought I would give feedback where I can. Please let me know if I can provide anymore information. I saw in some other posts that Eclipse generates a logfile. I would have included that but I was unable to locate it.
Do the hangs stop if you use 'eclipse -vmargs -Dosgi.locking=none' ?
If what Billy suggests works, that means your NFS setup has problems (another dup of bug 44735). Eclipse is trying to lock a file, and the call that tries locking a file never returns. Also, what is the VM being used?
I have a Gentoo Linux machine (x86), connected to another Gentoo Linux machine (SPARC) for an NFS share. The problem is that if Eclipse decided to rebuild the whole workspace (for some reason), it crashes the client machine. The server is fine, though. After this crash, any subsequent run of Eclipse will crash the machine because Eclipse keeps trying to rebuild the workspace. Another quirk related to this is: If I have multiple projects in the workspace, I need to import them one by one to let Eclipse build them one by one. If I import all projects (5 projects, total), Eclipse crashes just like I described above. So, when I encounter any crashes that involves rebuilding the whole workspace, I just delete workspace/.metadata directory and reimport every project one by one. Otherwise, Eclipse will play nice with NFS. I use NFS version 4 for both server and client. All other programs work perfectly fine. For some reason, Eclipse doesn't want to play nice under NFS 3, citing that the file system doesn't have locking capabilities. Client configuration: * Pentium III 933 MHz, using Linux kernel 2.6.11-gentoo-r4. * Sun's JDK 1.5.0_02-b09 on Linux x86. * NFS built into the kernel, with v4 support. No other parameters are involved * Workspace directory mounted as NFS version 4 share * Eclipse 3.1M5. Server configuration: * Ultra SPARC 10 440MHz, Linux kernel 2.6.9 * NFS built as module, with v4 support. No other parameters are involved * Server also acts as the CVS server.
Does the workaround in comment #1 avoid the hang for you? The error log file is located under workspace/.metadata/.log. If this file contains errors from around the time of any crash, error, or hang, please attach it here. Attach the log using the "Create a New Attachment" link. Finally, another useful piece of information you can provide is a stack trace at the time of the hang. Execute "kill -3 <pid>" Where <pid> is id of the Java process. This will produce a core file that you can also attach to this bug.
Also, note that this PR has nothing to do with crashes while running Eclipse, so you should report that problem as a separate PR.
The switch used in comment #1 does indeed resolve the issue. I am trying to understand what is incorrectly setup in my NFS environment that is causing this. If I find the cause, is there interest in me posting it to this bug for archival and search purposes? -G
Please do so (in bug 44735). Also, check out bug 44735 comment 51. *** This bug has been marked as a duplicate of 44735 ***
