Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 332541 - [RDT] Eclipse hangs when indexing (a large ptoject)at 99%
Summary: [RDT] Eclipse hangs when indexing (a large ptoject)at 99%
Status: RESOLVED WONTFIX
Alias: None
Product: PTP
Classification: Tools
Component: Remote Tools (show other bugs)
Version: 4.0.5   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-12-14 11:30 EST by Victor Liu CLA
Modified: 2018-06-08 09:58 EDT (History)
5 users (show)

See Also:


Attachments
Movie showing behavior of the C/C++ indexer over RDT/Remote Tools (618.36 KB, video/ogg)
2011-09-07 17:21 EDT, Corey Ashford CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Victor Liu CLA 2010-12-14 11:30:28 EST
When indexing a large project, Eclipse hangs at 99%.
Comment 1 Victor Liu CLA 2010-12-15 16:48:38 EST
1. To ensure that features using the index behave properly in the case of large, complex projects.

2. Download a large project from BOOST (http://www.boost.org/), and put it under your home directory on the remote machine. 

3. Create a Remote C/C++ project (Remote Provider: Remote tools, Project type: Empty project, Toolchains: Remote XL C/C++) on the directory with the large project.

4.  In the Project Explorer view, right click on the project choose "Index" -> "Rebuild".
Comment 2 Victor Liu CLA 2010-12-15 16:49:16 EST
1. To ensure that features using the index behave properly in the case of large, complex projects.

2. Download a large project from BOOST (http://www.boost.org/), and put it under your home directory on the remote machine. 

3. Create a Remote C/C++ project (Remote Provider: Remote tools, Project type: Empty project, Toolchains: Remote XL C/C++) on the directory with the large project.

4.  In the Project Explorer view, right click on the project choose "Index" -> "Rebuild".
Comment 3 Corey Ashford CLA 2011-09-07 17:21:35 EDT
Created attachment 202942 [details]
Movie showing behavior of the C/C++ indexer over RDT/Remote Tools

I'm seeing the identical behavior reported in this bugzilla.

I am trying to index the Linux kernel source on a remote machine.  Typically this takes about 20 minutes when the source is local.

Doing this using PTP/RDT/Remote Tools, it took about 20 minutes to get to 99% and then it just sits there at 9,038/9,039 sources, 1327 headers.  Also there are many other "Photran indexer (Waiting)" jobs waiting for the C/C++ Indexer job to complete.  It appears that they are completing, but slowly, and queued up behind the C/C++ indexer, perhaps halting its forward progress?  (just a guess)

And for some reason, the whole Progress view is flashing its contents on and off, as you can see in this attached video.
Comment 4 Corey Ashford CLA 2011-09-07 17:48:53 EDT
A couple of other things:

I've removed all of the Photran features I could find from my Eclipse client, but the Photran indexer is still coming up.

I'm seeing this error while using a Linux (Fedora 14) client, not WinXP, so I think the client OS is not relevant.
Comment 5 Chris Recoskie CLA 2011-09-16 10:55:02 EDT
Corey isn't seeing this any more.  See bug 357697
Comment 6 Corey Ashford CLA 2011-09-16 17:49:48 EDT
It's quite likely that what's being reported here is that the indexer is taking quite a lot of time to display all of the include files that it didn't locate.

When I indexed the Linux kernel source using all of the macro definitions from autoconf.h and a set of search paths allowing the indexer to find *most* of the include files, I still get quite a Unresolved Inclusions from the "drivers" subdirectory.  Apparently the drivers have their own include search paths for building, and so the CDT indexer doesn't find quite a good number of the include files because the paths to these include files weren't explicitly provided.

During the time that the indexer is spilling out all of these error message about Unresolved Inclusions, there are a bunch of Photran indexer jobs that start piling up waiting to run (I think).

Note that I'm still seeing this on the latest CDT (nightly build from Sep 15th + latest PTP 5.0.2 from the repo, dated Sept 1st).  It started happening again when I decided not to filter out the "drivers" subdirectory, and let the CDT indexer tackle the entire source tree.

So, I think that the latest CDT does a better job of finding include files (when include paths are provided), but if there are a lot of files that it can't find, and it spends a lot of time dumping all of the files it didn't find, then the photran indexer jobs start gumming up the works, and slowing it down to the point where very little progress is being made.
Comment 7 Greg Watson CLA 2018-06-08 09:58:28 EDT
This component has been deprecated.