Bug 73406 - Indexer: Double-Indexing on Specific Project
Summary: Indexer: Double-Indexing on Specific Project
Status: RESOLVED FIXED
Alias: None
Product: CDT
Classification: Tools
Component: cdt-core (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows XP
: P3 major (vote)
Target Milestone: 2.0.1   Edit
Assignee: Bogdan Gheorghe CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-09-07 16:33 EDT by Mathieu Lapensée CLA
Modified: 2004-09-09 16:28 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mathieu Lapensée CLA 2004-09-07 16:33:47 EDT
CDT 2.0.1 Build 200408271356

Double indexing on the TargetRTS source code (source is confidential).

Steps:
1) Extract TargetRTS File system into new workspace.
2) Create a standard project called "TargetRTS" on top of it.

Indexing starts.  Does it 2 times (once it did 3 times).
Comment 1 Bogdan Gheorghe CLA 2004-09-07 16:43:13 EDT
I'll have a look...
Comment 2 David Daoust CLA 2004-09-08 11:39:27 EDT
It is possible that this is happening when you
1. Create a project
2. Indexer runs in background
3. Do a build (which will cause the paths and symbols to update)
4. The path and symbol update will "dirty" the state of all files
5. Indexer will run on all the "dirty" files.
Comment 3 Mathieu Lapensée CLA 2004-09-08 13:29:35 EDT
Ok. I redid the test with workflow:

1) Create a Standard project
2) In properties, turn off indexer
3) Put the source in (import the file system or copy file over in explorer and 
refresh project in eclipse)
4) Build project
5) Turn on Indexer.
      Unfortunately, it indexes twice the whole project (1700+ files).  This 
is using our product with CDT 200408271356.
6) After the indexing is finished, do another build as another test to make 
sure that the indexer is not triggered again. 
      After executing it, the indexer was not triggered.
7) Close the project.
8) Open the project. 
      The indexer get triggered and does it
Comment 4 Mathieu Lapensée CLA 2004-09-08 13:31:03 EDT
Just to finish step 8.  It indexed the project once.
Comment 5 Bogdan Gheorghe CLA 2004-09-08 15:35:41 EDT
After investigation, it looks like there are 2 culprits at work here:

i) Importing a standard project, with Auto Build on, which triggers a build,
which kicks off the scanner discovery, which adds new include paths, which kicks
off a new index 

ii) A-OK bug: hitting Apply once you enable the indexer schedules a new indexing
job, so does hitting OK. So if you hit both of them, then you get 2 indexes...

- BG
Comment 6 Bogdan Gheorghe CLA 2004-09-09 16:28:18 EDT
Fixed - hitting apply or OK will trigger only one indexing job.

- BG