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 212207

Summary: Scanning never finishes
Product: editor Reporter: Petah
Component: Parsing & IndexingAssignee: Tomas Zezula <tzezula>
Status: RESOLVED DUPLICATE    
Severity: normal CC: vv159170
Priority: P3    
Version: 7.1   
Hardware: All   
OS: All   
Issue Type: DEFECT Exception Reporter: 186552
Attachments: stacktrace

Description Petah 2012-05-08 23:18:25 UTC
This bug was originally marked as duplicate of bug 207214, that is already resolved. This bug is still valid, so this seems to be another bug, but it might be related.

Build: NetBeans IDE 7.1.2 (Build 201204101705)
VM: Java HotSpot(TM) Client VM, 20.0-b11, Java(TM) SE Runtime Environment, 1.6.0_25-b06
OS: Windows 7

User Comments:
GUEST: ????????

vv159170: progress stops at 36% and never ends

vv159170: opened trunk/mercurial, opened one file from module using packages view
progress stopped at 43% and never moved (within 3 minutes)

petah: Scanning never finishes, and the IDE is unresonsive (can't even format code) while its scanning.
No indication of scan progress.




Stacktrace: 
java.lang.Exception: Scan canceled.
   at java.lang.Thread.getStackTrace(Thread.java:1479)
   at org.netbeans.modules.parsing.impl.indexing.LogContext.create(LogContext.java:110)
   at org.netbeans.modules.parsing.impl.indexing.LogContext.create(LogContext.java:103)
   at org.netbeans.modules.parsing.impl.indexing.PathRegistry.scheduleFirer(PathRegistry.java:775)
   at org.netbeans.modules.parsing.impl.indexing.PathRegistry.resetCacheAndFire(PathRegistry.java:769)
   at org.netbeans.modules.parsing.impl.indexing.PathRegistry.access$500(PathRegistry.java:83)
Comment 1 Petah 2012-05-08 23:18:31 UTC
Created attachment 119180 [details]
stacktrace
Comment 2 Tomas Zezula 2012-05-10 08:05:49 UTC
From the logs from the NB 7.1.2 where additional info like successive thread dumps were added:
The indexing is doing the HTML and CSS indexing.
Seems as duplicate of #207991

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