Community
Participate
Working Groups
Build Identifier: 3.7.0 I20100921-1024 Relating to closed fixed task ticket 318410. I have a large C project with about 200 relatively linked source. When I clean build a project, the CDT builder immediately begins the build process. Any build that isn't a clean build, there is a 10-17 second delay on my laptop (Core i7 MacBook Pro). The build window sticks at "Invoking CDT Builder". If I disable the indexer on the project, this doesn't happen. To disable the indexer I'm going into Project Properties->C/C++ General->Indexer and unchecking the Indexer option. The long delays on incremental build stalls workflow. If someone could share how I can give a stack trace I'd be happy to help. Reproducible: Always Steps to Reproduce: 1. Clean Build the project 2. Make a source change 3. Incrementally build the project, Invoking CDT Builder stalls for 10-17 seconds.
Are you using the Internal Builder or the Makefile builder? I think we use the indexer as a dependency generator, even with makefile builds... To report backtraces: http://wiki.eclipse.org/How_to_report_a_deadlock
Created attachment 179980 [details] Thread Dump immediately after building at "Invoking CDT Builder" This is the thread dump when I hit run, while the UI was "Invoking CDT Builder"
Created attachment 179981 [details] This is the thread dump when I hit run, while the UI was "Invoking CDT Builder" 15 seconds later. This is the thread dump when I hit run, while the UI was "Invoking CDT Builder" 15 seconds later.
I am using the external builder "make"
In the version of Eclipse (3.7M4), and CDT (I201012131338 M4) this issue seems to be resolved. The amount of delay is roughly 1 second now, which is a non-issue.
This is almost certainly a duplicate of bug 318410. The performance of #findFilesForLocation has been improved. *** This bug has been marked as a duplicate of bug 318410 ***
