Bug 107186 - StackOverflow Errors in Java Editor
Summary: StackOverflow Errors in Java Editor
Status: RESOLVED INVALID
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2005-08-17 04:31 EDT by alan flisch CLA
Modified: 2009-08-30 02:04 EDT (History)
1 user (show)

See Also:


Attachments
error log (105.99 KB, text/plain)
2005-08-17 04:34 EDT, alan flisch CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description alan flisch CLA 2005-08-17 04:31:34 EDT
eclipse.buildId=I20050627-1435
jdk1.5.0

I have been having problems with StackOverflowErrors on updating java files and
also using auto completes (ctrl-space) actions.  I assume these are related, but
the user experience is diffeerent.  For the auto complete issue, a "Internal
Error" dialog appears informing me of a stack overflow and for the updating the
java files issue I get a "An internal error occurred during: "Decoration
Calculation"." error dialog.

My projects have been imported from 3.0 and initially I was using a number of
plugins including MyEclipse and the VE.  However I have since started again with
a vanilla install of Eclipse 3.1 and am still having problems.

I began to suspect there was something corrupt about my project configuration or
something so I tried creating a new workspace first (in case anything was
corrupt there) and then a new project, copying all my src and supporting files
in.  Unfortunately I still experienced the auto complete stack overflow issue. 
I haven't replicated the other type that I was seeing yet though.

I'm afraid I can't think of a way to allow you to replicate this issue for
yourself, so I hope that you can make some sense of the attached error log. 
There are some stack traces which seem to indicate some recursion issues.
Comment 1 alan flisch CLA 2005-08-17 04:34:16 EDT
Created attachment 26181 [details]
error log
Comment 2 Frederic Fusier CLA 2005-08-17 08:47:04 EDT
Is it possible to zip and attach project to this bug?
If not, can you find a simple test case which reproduces this issue?
In both case, please provide info to get this exception in auto-completion (ie.
source code and position), thx
Comment 3 alan flisch CLA 2005-08-17 09:00:30 EDT
I'm afraid I can't, its confidential commercial work.
I have also been unable to find a simple way to replicate the problem.

Comment 4 Olivier Thomann CLA 2005-08-17 10:49:00 EDT
It would be nice to either isolate a simple test case or find a way for us to
get your actual test case.
This is the only way to get this fixed.
Comment 5 alan flisch CLA 2005-08-17 11:08:10 EDT
I appreciate that.  Unfortunatly I do not have the time at the moment to
experiment.  If you leave this open in the meantime I may at some point get the
chance to investigate further.
Comment 6 Ruth Alkema CLA 2005-11-10 11:07:48 EST
I am having the same problem.  I use eclipse 3.2M3 already for a couple of days
without problems, but since today I suddenly have this problem.
After a bit of experimenting it seems that the problems occur when I hit
ctrl-space for a class from a third-party library.  That is also something that
I can't remember doing in the previous days.

Starting with a clean workspace, older version of eclipse etc. did not solve the
problem.

maybe the problem is that the third-party jarfile is compiled with java 1.4 and
I use java 1.5?
Comment 7 Philipe Mulet CLA 2005-11-10 11:16:58 EST
Still it shouldn't do a stack overflow. As instructed before we need steps to
reproduce, etc...

Please reopen once required info is available.
Comment 8 alan flisch CLA 2006-05-22 04:50:44 EDT
I've tracked this problem down to a third party (commercial) library.  I'm not sure why it caused these issues, but replacing it with a newer version has resolved the issues.
Comment 9 Denis Roy CLA 2009-08-30 02:04:59 EDT
As of now 'LATER' and 'REMIND' resolutions are no longer supported.
Please reopen this bug if it is still valid for you.