Eclipse Community Forums: C / C++ IDE (CDT) » EXTREME slowness with CDT editor / indexer

Home » Language IDEs » C / C++ IDE (CDT) » EXTREME slowness with CDT editor / indexer(Experiencing extreme slowness with CDT editor and key input)

EXTREME slowness with CDT editor / indexer [message #1827449]

Thu, 14 May 2020 11:51

Eclipse User

The CDT editor / indexer is using 100% cpu usage for literally every character I try to type. It's gotten so bad that I have to wait about a second or so for literally every single character I try to type in the editor. Any text changes kicks up the CPU usage to 100%, fans go nuts.

I've got a C++ project, that unfortunately uses templates, this is CDT 9.11 on Mac.

Any ideas how I can fix the CPU usage?

It's gotten so bad that Eclipse is essentially useless.

Re: EXTREME slowness with CDT editor / indexer [message #1827452 is a reply to message #1827449]

Thu, 14 May 2020 14:35

Eclipse User

Try increasing the heap size. See https://www.eclipse.org/openj9/docs/xms/

EDIT: You can do this in the eclipse.ini file.

[Updated on: Thu, 14 May 2020 14:36] by Moderator

Re: EXTREME slowness with CDT editor / indexer [message #1827831 is a reply to message #1827449]

Mon, 25 May 2020 04:36

Eclipse User

Increasing heap value to
-Xms512m
-Xmx4096m
works and remove the heap size error. But I don't get index and autocomplete working for all code. Looks like didn't discovered some include files!

You know how is done the integration with cmakelists? If I include manually all "include folders" it works better.

Re: EXTREME slowness with CDT editor / indexer [message #1827878 is a reply to message #1827831]

Tue, 26 May 2020 04:28

Eclipse User

I am not 100% sure, but I think the indexer doesn't look into cmakelists. The alternative AFAIK is, as you say, to manually add all include folders.

To be sure you can ask on the CDT developers mailing list.

Re: EXTREME slowness with CDT editor / indexer [message #1828002 is a reply to message #1827878]

Thu, 28 May 2020 17:49

Eclipse User

The Indexer depends upon the user supplying macro definitions and header include paths.
There are a number of scanners (called Providers) which will add them automatically.
They are listed in
Project --> Properties --> C/C++ General --> Preprocessor Include Paths, Macros etc. --> Providers tab

The Build Output provider scans the build log looking for compiler calls and extracts the -I and -D info.
CMake default is to not show the compiler commands in the build output.
You can tell it to do so.
https://stackoverflow.com/a/2673355/3312726

Previous Topic:	Add custom tool to toolchain
Next Topic:	/<project>/build folder access denied

Goto Forum:

-=] Back to Top [=-

Current Time: Tue Jul 15 10:53:28 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter