Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Language IDEs » PHP Development Tools (PDT) » Eclipse consumes 100% CPU(An internal error occurred during: "Semantic Highlighting Job".)
Eclipse consumes 100% CPU [message #747986] Mon, 24 October 2011 12:04 Go to next message
Artiom Neganov is currently offline Artiom Neganov
Messages: 24
Registered: October 2009
Junior Member
I'm using Eclipse PDT
Version: Helios Release
Build id: 20100617-1415

Once I start it and open a PHP project Eclipse becomes slow: I see 2 eclipse processes consuming 100% of my CPU. Then an error message appears:

An internal error occurred during: "Semantic Highlighting Job".
java.lang.StackOverflowError


Any ideas what is this and why?
Re: Eclipse consumes 100% CPU [message #752351 is a reply to message #747986] Wed, 26 October 2011 11:11 Go to previous messageGo to next message
dominik is currently offline dominik
Messages: 122
Registered: July 2009
Senior Member
On 2011-10-24 14:04, Artiom Neganov wrote:
> I'm using Eclipse PDT
> Version: Helios Release
> Build id: 20100617-1415
>
> Once I start it and open a PHP project Eclipse becomes slow: I see 2 eclipse
> processes consuming 100% of my CPU. Then an error message appears:
>
> An internal error occurred during: "Semantic Highlighting Job".
> java.lang.StackOverflowError
>
> Any ideas what is this and why?

How long You have that? Is there any work in progress tab? It is normal that
Eclipse refresh and build project for first time or after incorrect shutdown.
For large project it can take some time but after that it's ready.

/dmc
Re: Eclipse consumes 100% CPU [message #752367 is a reply to message #752351] Wed, 26 October 2011 11:18 Go to previous messageGo to next message
Artiom Neganov is currently offline Artiom Neganov
Messages: 24
Registered: October 2009
Junior Member
dominik wrote on Wed, 26 October 2011 07:11

How long You have that? Is there any work in progress tab? It is normal that
Eclipse refresh and build project for first time or after incorrect shutdown.
For large project it can take some time but after that it's ready.
/dmc


A week maybe, since I got fresh install of Eclipse which I downloaded from the e.org website.

I don't remember what processes was there and I found the workaround: I disabled the Semantic Highlighting - it seems to be broken.

EDIT. It was a bug in PDT 2.1 which is evidently persisting in 2.2:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=312099

[Updated on: Wed, 26 October 2011 11:21]

Report message to a moderator

icon12.gif  Re: Eclipse consumes 100% CPU [message #846151 is a reply to message #747986] Sun, 15 April 2012 20:32 Go to previous messageGo to next message
Perry Anderson is currently offline Perry Anderson
Messages: 1
Registered: April 2012
Junior Member
I *think* I found it !!!

Given:

a) That Eclipse for PHP (Eclipse PDT) is updated just about everyday complete with daily builds. I can only assume this is from a team of very dedicated and competent developers who only want the same thing you do.

b) That only a small portion of us have been coming here complaining about our CPU maxing out while trying to edit PHP code.

Observations:

a) I have turned off just about every item in the preferences box to no avail.

Solutions:

In my past experience with software, especially large black boxes that normally work well for others. When faced with a situation that does not seem to respond to conventional theory... I like to do the unconventional. In this case... simply take care of the "little things".

In this particular case this means that I:

#1) Did an update via Help->Check for Software Updates
#2) Installed the latest updates
#3) Removed the old workspace and created a new one
#4) Paid attention to ALL THE WARNINGS, especially the YELLOW warnings which kept pointing to all the HTML errors in code that I either wasn't really using or meant to clean up anyway.

In other words...

Once I eliminated ALL THE WARNINGS.... The CPU stopped maxing out !!!

After updating the to latest Eclipse build and then taking the time to either fix the warnings and/or remove ALL unnecessary source code (that was slated to removed anyway)... the CPU returned to "normal".

In other words...

The problem was not that Eclipse PDT wasn't working properly...

...it was that it was working TOO GOOD !!!

It was doing precisely what it was designed to do... check ( & recheck ) for warnings in your source code while the keyboard was considered dormant.

So...

There you go...

Pay attention to ALL the warnings in your "Problems" window and do what it takes to reduce the number of warnings to ZERO !!!

And then report back here with your findings.

I honestly cannot believe just how well my Ubuntu 10.04 (32 bit) installation is operating on a $500 Compaq Presario. It's a dream and ALL I did was take care of the "little things".

Cheers,

Perry
Re: Eclipse consumes 100% CPU [message #875207 is a reply to message #846151] Tue, 22 May 2012 10:18 Go to previous messageGo to next message
N Oliver is currently offline N Oliver
Messages: 1
Registered: May 2012
Junior Member
I get warnings and errors on perfectly valid HTML. So while the warnings may contribute to the problem (which I share), for me they are not valid and are causing further problems.

Also, I don't control all the code that the semantic parser thinks it needs to index, so even if there *is* invalid code where I'm not working, fixing the problems (no matter how much my type-A brain wants to) are not an option. This approach might work with smaller projects (and I have my fair share) but it's distant from a true fix.

Between this issue and egit's premature push to predominant usage, my development times have been taking longer and longer. Pity, as I love Eclipse otherwise Sad
Re: Eclipse consumes 100% CPU [message #882565 is a reply to message #747986] Wed, 06 June 2012 18:36 Go to previous message
jon jones is currently offline jon jones
Messages: 1
Registered: June 2012
Junior Member
After applying the updates and removing the errors in all my files, I no longer get the semantic error message. Works for me.
Previous Topic:How do I get the style and script tags to close automatically?
Next Topic:Xdebug and RSE - wrong path (and other questions)
Goto Forum:
  


Current Time: Thu Oct 23 16:01:31 GMT 2014

Powered by FUDForum. Page generated in 0.01833 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software