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 174041 - [68cat] [exceptions] Following Exception, System Scans Projects
Summary: [68cat] [exceptions] Following Exception, System Scans Projects
Status: RESOLVED INVALID
Alias: None
Product: ruby
Classification: Unclassified
Component: Code (show other bugs)
Version: 6.x
Hardware: PC Linux
: P3 blocker (vote)
Assignee: Erno Mononen
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-08 06:59 UTC by esmithbss
Modified: 2009-10-08 09:04 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
IDE Log File (116.62 KB, text/plain)
2009-10-08 07:00 UTC, esmithbss 		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 esmithbss 2009-10-08 06:59:12 UTC 
[ BUILD # : 200910071536 ]
[ JDK VERSION : 1.6.* ]

It appears that following any exception generation or reporting, the
system returns to scanning the projects which takes excessive amounts
of time based on the number of Gems installed.
Comment 1 esmithbss 2009-10-08 07:00:01 UTC 
Created attachment 89075 [details]
IDE Log File
Comment 2 Erno Mononen 2009-10-08 09:04:58 UTC 
I believe this is by design, exceptions don't necessarily need to affect indexing in any way - this way the system can 
continue working even after exceptions. E.g. in this particular case the thrown AE affected indexing of only some file
(s), other files were indexed normally. Of course, the goal is to not have any exceptions during scanning in FCS.. :)