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 218538 - background scanning and no end :-(((
Summary: background scanning and no end :-(((
Status: RESOLVED DUPLICATE of bug 217213
Alias: None
Product: javaee
Classification: Unclassified
Component: JSF (show other bugs)
Version: 7.2
Hardware: All All
: P3 normal (vote)
Assignee: Martin Fousek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-09-18 13:29 UTC by Exceptions Reporter
Modified: 2012-10-12 12:51 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 192531


Attachments
stacktrace (2.58 KB, text/plain)
2012-09-18 13:29 UTC, Exceptions Reporter
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Exceptions Reporter 2012-09-18 13:29:47 UTC
This issue was reported manually by sdedic.
It already has 1 duplicates 


Build: NetBeans IDE 7.2 (Build 201207171143)
VM: Java HotSpot(TM) 64-Bit Server VM, 20.8-b03, Java(TM) SE Runtime Environment, 1.6.0_33-b03
OS: Windows 7

Stacktrace: 
java.lang.Exception: Scan canceled.
   at java.lang.Thread.getStackTrace(Thread.java:0)
   at org.netbeans.modules.parsing.impl.indexing.LogContext.create(LogContext.java:113)
   at org.netbeans.modules.parsing.impl.indexing.LogContext.create(LogContext.java:106)
   at org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater.fileChangedImpl(RepositoryUpdater.java:779)
   at org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater.access$5800(RepositoryUpdater.java:139)
   at org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$FCL.fileChanged(RepositoryUpdater.java:5765)
Comment 1 Exceptions Reporter 2012-09-18 13:29:50 UTC
Created attachment 124514 [details]
stacktrace
Comment 2 Svata Dedic 2012-09-18 13:30:38 UTC
There's a JSF / webapp related exception in the reporters message log; please evaluate.
Comment 3 Martin Fousek 2012-10-12 12:51:23 UTC
That class went through 2-3 quite big changes since that time and especially the last fix prevents situations like that. It checks the DocumentBase for the null value.

Marking as duplicate of issue #217213 since it's most related change which prevents that for sure.

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