This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 215108 - IDE freezes during code completion in a groovy script with several inner class
Summary: IDE freezes during code completion in a groovy script with several inner class
Status: RESOLVED DUPLICATE of bug 216992
Alias: None
Product: groovy
Classification: Unclassified
Component: Editor (show other bugs)
Version: 7.2
Hardware: PC Windows 7 x64
: P3 normal (vote)
Assignee: Martin Janicek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-07-03 07:34 UTC by kzwaga
Modified: 2012-08-20 12:23 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Source that can reproduce the issue (2.07 KB, application/octet-stream)
2012-07-03 07:34 UTC, kzwaga 		Details
messages.log (47.66 KB, application/octet-stream)
2012-07-03 07:37 UTC, kzwaga 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description kzwaga 2012-07-03 07:34:21 UTC 
Created attachment 121683 [details]
Source that can reproduce the issue

If you trigger code completion in the groovy script with several inner class, IDE freezes up.

You can easily reproduce the issue as stated below:
1)Simply create groovy standalone project by File->New Project->Samples->Groovy->Groovy Java Demo.
2)Place attached CaluculateZodiacSign.groovy anywhere under source package.
3)Open CaluculateZodiacSign.groovy
4)Type some word and pless ctrl+SPACE anywhere in the code.

Naturally you must have groovy support installed.
Comment 1 kzwaga 2012-07-03 07:37:02 UTC 
Created attachment 121684 [details]
messages.log

Attached messages.log but that will not help.
Comment 2 Martin Janicek 2012-08-16 08:59:15 UTC 
Huh, you're right. Reproducible and valid issue. Definitely needs to be done for 7.3. Thanks you for the report!
Comment 3 Martin Janicek 2012-08-20 12:23:58 UTC 

*** This bug has been marked as a duplicate of bug 216992 ***