tag:blogger.com,1999:blog-5269145473984771170.post4965572319891119765..comments2023-12-13T23:25:55.427-08:00Comments on Bunwich: Eclipse Helios PDT and 50% CPU Usagebunwichhttp://www.blogger.com/profile/02484589527149322731noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-5269145473984771170.post-90171788222726913482012-06-09T22:45:26.394-07:002012-06-09T22:45:26.394-07:00I'm going to have to keep my eye out the next ...I'm going to have to keep my eye out the next time I see the cpu maxing out. I've upgraded my computer once since I wrote this post and the 4 gig of mem with pdt 3.0.0 has kept this problem under check.<br /><br />Thanks for the update.bunwichhttps://www.blogger.com/profile/02484589527149322731noreply@blogger.comtag:blogger.com,1999:blog-5269145473984771170.post-26375201732615159302012-04-15T17:46:53.710-07:002012-04-15T17:46:53.710-07:00I *think* I found it !!!
Given:
a) That Eclipse ...I *think* I found it !!!<br /><br />Given:<br /><br />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.<br /><br />b) That only a small portion of us have been coming here complaining about our CPU maxing out while trying to edit PHP code.<br /><br />Observations:<br /><br />a) I have turned off just about every item in the preferences box to no avail.<br /><br />Solutions:<br /><br />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".<br /><br />In this particular case this means that I:<br /><br />#1) Did an update via Help->Check for Software Updates<br />#2) Installed the latest updates<br />#3) Removed the old workspace and created a new one<br />#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.<br /><br />In other words...<br /><br />Once I eliminated ALL THE WARNINGS.... The CPU stopped maxing out !!!<br /><br />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".<br /><br />In other words...<br /><br />The problem was not that Eclipse PDT wasn't working properly...<br /><br />...it was that it was working TOO GOOD !!!<br /><br />It was doing precisely what it was designed to do... check ( & recheck ) for warnings in your source code while the keyboard was considered dormant.<br /><br />So...<br /><br />There you go...<br /><br />Pay attention to ALL the warnings in your "Problems" window and do what it takes to reduce the number of warnings to ZERO !!!<br /><br />And then report back here with your findings.<br /><br />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".<br /><br />Cheers,<br /><br />PerryPerry A.https://www.blogger.com/profile/11084003474491396920noreply@blogger.com