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

Bug 42438

Summary: problems with projects having recursive links on linux
Product: [Eclipse Project] Platform Reporter: Thoralf Hänsel <thoralf>
Component: ResourcesAssignee: John Arthorne <john.arthorne>
Status: RESOLVED WORKSFORME QA Contact:
Severity: normal    
Priority: P3 CC: dj.houghton
Version: 3.0   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
Whiteboard:

Description Thoralf Hänsel CLA 2003-09-03 07:17:48 EDT
Overview Description: Eclipse has various problems with projects having
recursive links on linux (e.g. "ln -s . core" created in the base directory of
the project); sometimes resulting in system crashes caused by
java.lang.OutOfMemoryErrors

Steps to Reproduce:
1) create a project with the following structure:
   projectdir/src/Test.java
   with projectdir as the base directory of the project and Test.java as a
simple java file without having a package delaration
2) in projectdir create a recursive link, e.g. using
   cd projectdir
   ln -s . core
3) import the project to eclipse with the following steps:
   - File --> New --> Project
   - Select "Java Project"
   - Choose projectdir as the Project contents, enter a project name and press
the "Finish" button

Actual Results:
* 41 errors (The declared package doesn't match the expected package ...)!
* try Search --> File Search with
  - Containing Text: Test
  - File name patterns: *
  which results in 41 search results
* trying the same things in bigger projects multiplies the problems: a project
having only about 100 source files tries to find search results in about 45.000
files; opening, closing, and deleting these projects sometimes results in system
crashes caused by java.lang.OutOfMemoryErrors

Expected Results:
* recursive links should be ignored or handled somehow

Build Date & Platform: SuSE Linux 8.1, Eclipse 3.0 M3 GTK (28 Aug 2003)
System configuration: Athlon 2GHz, 512MB RAM,
Comment 1 DJ Houghton CLA 2004-05-17 13:05:58 EDT
Verified still a problem with i0514-0800.
Comment 2 John Arthorne CLA 2005-04-29 15:35:02 EDT
John to investigate if a simple fix is possible for 3.1. Otherwise this is
likely to be deferred.
Comment 3 John Arthorne CLA 2005-05-02 17:32:03 EDT
I cannot reproduce a problem in I20050426. (3.1 development stream)