Community
Participate
Working Groups
Build Identifier: 20100617-1415 I have seen many other issues describing this or similar problems. They are all marked as closed and fixed. I have a later build than all of them - 20100617-1415 E.G #315337 - Resolved fixed (This mentions fix available by building from source only - is mine a duplicate of this?) #315989 - Fixed at PDT-2.2.0.v20100616 (I have later build) #308145 - Fixed at S201006090518 (2010/06/09) (I have later build) #313410 - Closed on 2010-05-27 (I have later build) #308896 - Closed on 2010-05-17 (I have later build) #314916 - Verified at PDT-2.2.0.v20100616 (I have later build) #316876 - Retested at PDT-2.2.0.v20100616 (I have later build) #301430 - No longer reproducible EclipsePdt 2.2.0.v20100504 (I have later build) #302871 - Closed on 2010-05-13 (I have later build) Reproducible: Always Steps to Reproduce: 1. Open the editor into a PHP project 2. Edit some files for a while 3. After 2 - 3 minutes, stack overflow and graceful crash. Unfortunately I can't isolate it to a single file, and nor can I post any example PHP files as I can't put the code into the public domain.
Created attachment 176954 [details] Eclipse error log file
Hi,can you attach your php file that can reproduce this bug.we really have fixed a bug with the same error log,thanks!
Hi zhaozhongwei, Unfortunately I'm not able to attach the PHP file(s) causing the issue as I'm not authorized to put the code in the public domain. I realize that makes it really difficult for you, but there's nothing I can do about it. I just had a thought though, I was following the instructions on the bug report pages, and getting my build id from Help / About Eclipse. But that's not necessarily the version of PDT I'm using right? I have now gone to Help / Install new software, and looked up the version of PHP PDT that I have. This shows: PHP Development Tools (PDT) SDK Feature 2.2.0.v20100519-1400-53-84QAN2IGRoLXQNHWOXe1La9Od And 20100519 *is* *earlier* than some of the resolved bugs I found. Do I need to download and update to a later PDT version?
Thanks for your quick reply!I check the code again,the code change a lot and the method causing the stack overflow has been removed!
Yes,I think a later PDT version will help you resolve this issue(we change it recently,7/14),but I do not know where to download it,because there is no nightly build for a long time,we will try to fix it asap:)
(In reply to comment #5) > Yes,I think a later PDT version will help you resolve this issue(we change it > recently,7/14),but I do not know where to download it,because there is no > nightly build for a long time,we will try to fix it asap:) So what is the actual solution? I tried uninstalling PDT from eclipse, and reinstalling what I *think* is a later release - from http://www.eclipse.org/downloads/download.php?file=/tools/pdt/downloads/drops/2.2.0/S201006090518/pdt-Update-S201006090518.zip But even though I uninstalled eclipse and restarted, installing the new update site zip doesn work, it just says that PDT is already installed. So.... should I download a non PDT Eclipse platform, perhaps Eclipse classic, then install pdt-Update-S201006090518.zip into that? It would be good to document a solution here, on how to actually get up and running with PDT, because the live release download that the site points everyone to download, currently has this show stopping bug that makes the IDE unusable.
as i said,we fixed it on 2010-07-14.
> I tried uninstalling PDT from eclipse, and reinstalling what I *think* is a > later release - from > http://www.eclipse.org/downloads/download.php?file=/tools/pdt/downloads/drops/2.2.0/S201006090518/pdt-Update-S201006090518.zip OK - even though the date "S201006090518" is later, that doesn't mean its a new release. That's still the 2.2.0.v20100519 release (and still crashing when I use it from withing eclipse classic)
so,the bug still exists in the latest release,but I mean it has been fixed in cvs head(source code),so please wait for next release,thanks!
(In reply to comment #7) > as i said,we fixed it on 2010-07-14. Yes but for all the people googling and finding this page, it would be nice for them to find a set of steps to actually get up and running on PDT. Because even though it is fixed on 2010-07-14, that fix is not available to all but the most advanced users who can check out from CVS and build. I've just looked in to what would be required to check out from CVS and build myself, but that looks way too complicated for most PHP developers - I found a checkout "script" and something about "maps" - which implies a big learning curve. I tried turning off all the builders and validators as well, to try to disable whatever PDT functionality is crashing it, and that didn't work. So for now, I'll use nano and fgrep, and wait for the next PDT release. Do you know when the next release is planned?
I have told you that the nightly build has some problem when we fix this,you can download nightly build which is build from the source code.and I think there will be a long time for the next release,I am very sorry for this:(
hi Willie Can I mark this bug as fixed,so our QA can verify it,we can do nothing leave it reopen,one think we could do is to wait for the next release,right?
fixed already
Well technically this bug is fixed, but the issue is not. It's a pretty big show stopper that everyone who downloads PDT is downloading a PHP editor that can't edit PHP. Nightly builds aren't available with the fix, so there is no resolution. Perhaps I should I open a separate ticket requesting that nightly builds be fixed and a notice be placed on the download page that the latest nightly build should be downloaded and not the latest (un)stable release???
+1 for this issue. Happens on my installation under Windows 7 too. Processing Dirty Regions & Syntax Highlighting Overflow error. Makes working with PDT PITA :|
(In reply to comment #15) > +1 for this issue. > Happens on my installation under Windows 7 too. > Processing Dirty Regions & Syntax Highlighting Overflow error. > Makes working with PDT PITA :| I have added a request re fixing nightly builds over at https://bugs.eclipse.org/bugs/show_bug.cgi?id=325817
Thank you Willi - have now voted for this issue too ;)
Downloaded latest nightly directly from hudson. Looks very good at the moment! Thank you very much.
(In reply to comment #19) > fixed already Stop repeating that **** man. I am experience this issue 3 months later and all I see is you repeating 'fixed already', which first is not a full sentence even and second OBVIOUSLY ISN'T
So... if this was fixed on 14-Jul, is the fix in downloadable 2.2.1.M201010110334 ? This seems to be also the version found in the Helios SR2 version of the PHP all-in-one package. I'm confused by the way bugs are tracked here... what release Stream does "HEAD" refer to, 2.2.x or 3.0 ? And what Stream does "branch" refer to? And in what plugin or file has this been fixed? I downloaded Zend Studio 8.0 and noticed that some of the org.eclipse.php plugins in there carry a version number from the 2.2.x Stream but newer than anything available from Eclipse.org. So if Zend can fix bugs in the 2.2.x Stream for Studio, why can't the same fixes be made available for download to the Community? This is a P1 kind of problem which doesn't only affect PDT but all of Eclipse so I'd really appreciate some clarification here.
Ok, it looks like a recent 2.2.x build is available from https://hudson.eclipse.org/hudson/job/cbi-pdt-2.2-helios/lastSuccessfulBuild/artifact/build/ Would this issue be fixed in there? Is it adviseable to use an N-build for production use?
Doing a little bit of CVS archaeology reveals org.eclipse.php.core/MethodReturnTypeEvaluator@@1.23.2.1 as a potential candidate holding the fix. If that is true then the fix should be in the 2.2.1.M201010110334 build available from PDT/Downloads and the Helios SR2 PHP all-in-one package. Can somebody confirm?
The pdt-2.2 builds on hudson are currently broken due to a simple typo in the URL fetching the Eclipse sdk. I attached a patch on bug 325817, please consider applying.
The issue is not longer reproducible. Feel free to reopen if you meet it again, but share the scenario. Closing...
