|Re: [cdt-dev] How can I prevent the indexer taking over the entire CPU?|
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>
>> 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
>> Can anyone suggest any way to prevent this from happening?
>> Thanks in advance
>> cdt-dev mailing list
>> To change your delivery options, retrieve your password, or unsubscribe
>> from this list, visit
> cdt-dev mailing list
> To change your delivery options, retrieve your password, or unsubscribe from
> this list, visit
Back to the top