GRECLIPSE

StackOverflow while editing groovy classes.

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Critical Critical
  • Resolution: Fixed
  • Affects Version/s: 2.5.1Release
  • Fix Version/s: 2.5.2.Release
  • Component/s: Editor
  • Labels:
    None
  • Environment:
  • Number of attachments :
    2

Description

The error is very similar to GRECLIPSE-1116.

Create a groovy file with several class descriptions. Begin editing one of the classes and a stack overflow error occurs. After closing eclipse, attempts to start eclipse result in stack overflow errors.

The attached groovy file is the one that generated the errors. I was editing the ExactString class line 50 when the errors occurred. Try the following steps.

1) Type enter after line 49 – super.run(expectedValue, actualValue)
2) On the new blank line 50 type: if (!TokenCompiler.isKeyWord(expectedValue)) {

The stack overflow is thrown after the open parentheses is typed.

Work around for the error:
1) close eclipse
2) Opening the groovy file in a text editor reveals that the edits were partially saved.
3) Complete the edits in the text editor and save the file.
4) Open eclipse and the stack overflow error no longer occurs.

  1. Text File
    .bak_5.log
    10/Oct/11 12:51 PM
    1.04 MB
    Frank Fuller
  2. File
    CompareJSON.groovy
    10/Oct/11 12:51 PM
    6 kB
    Frank Fuller

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Andrew Eisenberg added a comment -

It looks to me like you are having a temporary circular class hierarchy. See GRECLIPSE-531. It should have been resolved in 2.5.0, so you may be seeing a new variation of the problem.

I did try your instructions in 2.5.2 and could not reproduce the problem. Could you try updating to 2.5.2 and seeing if you stil have the problem?

Show
Andrew Eisenberg added a comment - It looks to me like you are having a temporary circular class hierarchy. See GRECLIPSE-531 . It should have been resolved in 2.5.0, so you may be seeing a new variation of the problem. I did try your instructions in 2.5.2 and could not reproduce the problem. Could you try updating to 2.5.2 and seeing if you stil have the problem?
Hide
Permalink
Frank Fuller added a comment -

Andrew,

I updated to the 2.52 plugin. Prior to conducting the update, I verified that the error still occurs, and I left the partially edited file in the work space. I upgraded the plugin, restarted eclipse and attempted to open the work space that had the error. The work space opened without the stack overflow and the partially edited file was visible. I completed the edits, saved the file, undid the changes, and attempted to recreate the error. I did not receive the stack overflow error after updating. So, it appears that the bug is fixed in 2.5.2.

Thank you for your very quick assistance in resolving this issue.

Show
Frank Fuller added a comment - Andrew, I updated to the 2.52 plugin. Prior to conducting the update, I verified that the error still occurs, and I left the partially edited file in the work space. I upgraded the plugin, restarted eclipse and attempted to open the work space that had the error. The work space opened without the stack overflow and the partially edited file was visible. I completed the edits, saved the file, undid the changes, and attempted to recreate the error. I did not receive the stack overflow error after updating. So, it appears that the bug is fixed in 2.5.2. Thank you for your very quick assistance in resolving this issue.
Hide
Permalink
Frank Fuller added a comment -

Upgrading to the 2.5.2 version of the plugin resolved the issue.

Show
Frank Fuller added a comment - Upgrading to the 2.5.2 version of the plugin resolved the issue.
Hide
Permalink
Andrew Eisenberg added a comment -

Thanks for verifying the fix.

Show
Andrew Eisenberg added a comment - Thanks for verifying the fix.

People

  • Assignee:
    Andrew Eisenberg
    Reporter:
    Frank Fuller
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: