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.
Build: NetBeans IDE 7.1 (Build 201112071828) VM: Java HotSpot(TM) Client VM, 20.5-b03, Java(TM) SE Runtime Environment, 1.6.0_30-b12 OS: Windows 7 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:74) at org.netbeans.modules.parsing.impl.indexing.LogContext.create(LogContext.java:67) at org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater.scheduleWork(RepositoryUpdater.java:1297) at org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater.propertyChange(RepositoryUpdater.java:1042) at java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:339)
Created attachment 115848 [details] stacktrace
Report 'analysis': Report #560853, #560817, #560757 According to the logs, Maven projects are being opened, then scanning starts & finishes and starts again, WHILE still opening maven projects. No harmful message found in message log. Possibly some deadlock between indexer & some other action in the IDE ? * Maven EE projects * J2EE installation (modules enabled) Report #559584 * apparently SOME indexing finished * Indexing started after GIT pull (7:17), unfinished (cancelled at 8:30) * Indexing apparently cancelled after some editing in the IDE * NOT on startup ! Report #557489, #552160 * one PHP project opened * indexing at startup did not finish Report #555181 * cancelled within 1 minute after indexing start * on startup with NO PROJECTS opened ? All except #559584 happen on IDE startup, during up-to-date check ? Dao - if you happen to get to this situation again, could you please shot and attach here thread dump BEFORE you cancel the scanning (http://wiki.netbeans.org/GenerateThreadDump) ?
Maven and PHP exception reports reassigned to their appropriate exception reports. The remainder is report #559584, where the PHP scanning is slow/stopped. Need more info for that, try to reproduce with 7.1.2 or dev build