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 200456 - Scanning projects source for hours : RequestProcessor at 30% cpu
Summary: Scanning projects source for hours : RequestProcessor at 30% cpu
Status: RESOLVED DUPLICATE of bug 180230
Alias: None
Product: groovy
Classification: Unclassified
Component: Editor (show other bugs)
Version: 7.0
Hardware: PC Windows 7 x64
: P2 normal (vote)
Assignee: Petr Hejl
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-28 08:31 UTC by luca.rancan_dbalab.it
Modified: 2011-09-14 10:08 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Snapshot after 20 min (70.34 KB, application/octet-stream)
2011-07-28 08:31 UTC, luca.rancan_dbalab.it
Details
ide log after 30 min (418.76 KB, application/octet-stream)
2011-07-28 08:33 UTC, luca.rancan_dbalab.it
Details
entire ide log (657.50 KB, application/octet-stream)
2011-07-28 09:24 UTC, luca.rancan_dbalab.it
Details

Note You need to log in before you can comment on or make changes to this bug.
Description luca.rancan_dbalab.it 2011-07-28 08:31:52 UTC
Created attachment 109656 [details]
Snapshot after 20 min

Hi,
I am having a problem similar to Bug 175320 Comment #9 : 
NB scans project source for hours when I open the IDE.
In the log there are many [Error] ...GroovyParser...
RequestProcessor takes 30 % cpu .
I have a Ggrails application with 182 source files, 
no error in task window and only 4 plugins. 

My grails project uses :
- Grails 1.3.5
- Groovy 1.7.5
with the following plugins:
breadcrumbs(0.5.2)
hibernate(1.3.5)
quartz(0.4.2)
tomcat(1.3.5)

I attach the entire log and the cpu snapshot .
Thanks

Luca(R)
Comment 1 luca.rancan_dbalab.it 2011-07-28 08:33:37 UTC
Created attachment 109657 [details]
ide log after 30 min
Comment 2 luca.rancan_dbalab.it 2011-07-28 09:24:06 UTC
Created attachment 109662 [details]
entire ide log
Comment 3 Petr Hejl 2011-09-14 10:08:05 UTC

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