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 234747 - unable to cancel scanning
Summary: unable to cancel scanning
Status: REOPENED
Alias: None
Product: editor
Classification: Unclassified
Component: Parsing & Indexing (show other bugs)
Version: 8.0
Hardware: All All
: P3 normal with 3 votes (vote)
Assignee: Tomas Zezula
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-08-21 20:13 UTC by miked_187
Modified: 2018-04-14 06:41 UTC (History)
13 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 795519


Attachments
stacktrace (1.50 KB, text/plain)
2013-08-21 20:13 UTC, miked_187
Details

Note You need to log in before you can comment on or make changes to this bug.
Description miked_187 2013-08-21 20:13:21 UTC
Build: NetBeans IDE 7.4 Beta (Build 201307092200)
VM: Java HotSpot(TM) 64-Bit Server VM, 23.25-b01, Java(TM) SE Runtime Environment, 1.7.0_25-b17
OS: Windows 7

User Comments:
GUEST: started netebeans ang got tired of waiting on not moving process

GUEST: When we start the Netbeans, the background scanning too too much time and gets hang in between the coding process

GUEST: ?????????? "??????? ???????????? ????????" ? ????????? "?????????" ,  ?????????? ?????????, ????????????? ??? ????????????. ???????????? ????????? ???? ?? ????????. ?????? ?????? ??? ?? ?????!

GUEST: Seems that "git pull" and "background scanninc projects" are blocking each other.

GUEST: background scanning is stuck at 80% and prevents action item scanning

ostermann_bernd: Starting netbeans 7.3.1

miked_187: 83% and stalled, system at 80%+ of cpu

GUEST: Copying a class from a 7.3.1 project to a new project created under the beta.

GUEST: Running like a dog!




Stacktrace: 
org.netbeans.modules.parsing.impl.indexing.ScanCancelledException: Scanning cancelled
   at java.lang.Thread.getStackTrace(Thread.java:1568)
   at org.netbeans.modules.parsing.impl.indexing.LogContext.create(LogContext.java:131)
   at org.netbeans.modules.parsing.impl.indexing.LogContext.create(LogContext.java:124)
   at org.netbeans.modules.parsing.impl.indexing.PathRegistry.scheduleFirer(PathRegistry.java:829)
   at org.netbeans.modules.parsing.impl.indexing.PathRegistry.resetCacheAndFire(PathRegistry.java:822)
   at org.netbeans.modules.parsing.impl.indexing.PathRegistry.access$500(PathRegistry.java:86)
Comment 1 miked_187 2013-08-21 20:13:23 UTC
Created attachment 139027 [details]
stacktrace
Comment 2 miked_187 2014-05-21 21:45:16 UTC
same problem with NB 8, perhaps even worse

Product Version: NetBeans IDE 8.0 (Build 201403101706)
Updates: NetBeans IDE is updated to version NetBeans 8.0 Patch 1.1
Java: 1.7.0_25; Java HotSpot(TM) 64-Bit Server VM 23.25-b01
Runtime: Java(TM) SE Runtime Environment 1.7.0_25-b17
System: Windows 7 version 6.1 running on amd64; Cp1252; en_US (nb)
User directory: C:\Users\mike\AppData\Roaming\NetBeans\8.0
Cache directory: C:\Users\mike\AppData\Local\NetBeans\Cache\8.0

Opening big C++ or Java projects on the same remote share have no issues with opening projects or scanning projects, just PHP
Comment 3 Tomas Zezula 2014-05-22 06:55:13 UTC
In reply to comment 2:
Please in case when the problem is language specific (PHP in your case) reassign the issue directly to the affected language (PHP). It makes evaluation much faster.
Created a new issue: https://netbeans.org/bugzilla/show_bug.cgi?id=244649
Comment 4 nedenom 2014-08-07 11:02:38 UTC
Please let us be able to cancel scanning, so we don't have to sit and wait 15 minutes for it to complete while the IDE is unusable. I'd rather have an option to start scanning manually.
Comment 5 miked_187 2014-08-07 14:00:18 UTC
I keep getting notifications on this issue that will clearly never be addressed.  I'd prefer not to have the aggravation, so since I can't remove myself from the issue I'm closing it so that I don't have see it any more.
Comment 6 NoBugs 2015-03-11 05:22:00 UTC
I think something much more serious is happening here - as you can see there were a dozen exception-reports today alone that are getting marked as duplicate of this bug.

I saw this on both computers I use Netbeans on regularly and this makes it basically unusable except as a cpu-hogging text editor. Please please fix! or many users will have to switch to not-so-useful text-editors :(
Comment 7 miked_187 2015-03-13 14:36:35 UTC
can someone remove me as the POC for this issue. 

I've moved on to phpstorm and no longer use NB, mostly due to this issue, and no longer want to be part of this bug and its reports.
Comment 8 coladict 2018-04-13 11:10:17 UTC
Clearly NOT fixed in 2015 as it is marked. There's a lot of people who choose to send in the reports all the time. http://statistics.netbeans.org/analytics/detail.do?id=201530