Re: [cdt-dev] How can I prevent the indexer taking over the entire CPU?

[Steve Lorimer <steve.lorimer@xxxxxxxxx>]

Not sure if this is of any help.

I start eclipse, and it immediately starts running the indexer, which seems to take forever, and top shows several 100% CPU usage.

If I shut it down, and restart, the same thing happens.

So I ran it through strace, the output of which is attached. As I said, not sure if it's of any help, but hopefully so!

On 18 March 2016 at 09:43, Doug Schaefer <cdtdoug@xxxxxxxxx> wrote:

jstack dumps periodically would be the best way to do it. We need to know where in the indexer it's stuck so look for org.eclipse.cdt.core type classes in the stacks, especially if they show up time after time. If you have a way to do some memory analysis, you could also see what objects are filling up memory.

On Fri, Mar 18, 2016 at 5:20 AM, Bossert, Andre <anb0s@xxxxxxxx> wrote:

We have similar issues at Windows 7 64bit with Luna and Mars releases,
but not with Kepler. During indexing all 4 or 8 cores are at 96% load
and Eclipse is not responsive or slow for 15-20 minutes sometimes. If
we file a bug request, what should be attached to the bug report? How
can we analyse it? Log files, dumps etc...

2016-03-17 14:51 GMT+01:00 Doug Schaefer <cdtdoug@xxxxxxxxx>:
> Sounds like a bug, please raise one. I used to see this when indexing boost.
> But I haven't tried lately.
>
> On Thu, Mar 17, 2016 at 9:22 AM, Steve Lorimer <steve.lorimer@xxxxxxxxx>
> wrote:
>>
>>
>> On 16 March 2016 at 15:09, Doug Schaefer <cdtdoug@xxxxxxxxx> wrote:
>>>
>>> You have parallel garbage collection happening and it's the 8 threads
>>> your talking about. Have you tried making your Xmx bigger? I'm guessing the
>>> indexer is causing you to run out of Java heap
>>
>>
>> Is there any way to prevent this from happening?
>>
>> What exactly is happening in the indexer that causes 8 GC threads to spin
>> up to 100%?
>>
>> If I set -Xmx8G for the --launcher.appendVmargs section in eclipse.ini
>> does that mean I have 8GB heap? Why does the indexer blow through the 8GB
>> heap?
>>
>> Can anyone suggest any way to prevent this from happening?
>>
>> Thanks in advance
>> Steve
>>
>> _______________________________________________
>> cdt-dev mailing list
>> cdt-dev@xxxxxxxxxxx
>> To change your delivery options, retrieve your password, or unsubscribe
>> from this list, visit
>> https://dev.eclipse.org/mailman/listinfo/cdt-dev
>
>
>
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from
> this list, visit
> https://dev.eclipse.org/mailman/listinfo/cdt-dev

--
Regards
Andre (anb0s)
eMail: anb0s@xxxxxxxx

_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cdt-dev

_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cdt-dev

Attachment: eclipse.strace.out.gz
Description: GNU Zip compressed data