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 258376 - Background scanning of projects never ends
Summary: Background scanning of projects never ends
Status: NEW
Alias: None
Product: ide
Classification: Unclassified
Component: Code (show other bugs)
Version: 8.1
Hardware: PC Windows 7
: P3 normal with 1 vote (vote)
Assignee: issues@ide
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-03-15 11:17 UTC by otisjenkins85
Modified: 2017-08-11 09:01 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
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 otisjenkins85 2016-03-15 11:17:04 UTC 
Background scanning of projects never ends, and if I try to end it I get the message "Scanning cancelled too early."  It also causes problems when other processes can't run because the background scanning never finishes.

This seems to happen in every version of Netbeans, and every time it gets fixed it happens again in a later version.  I'd almost go as far as to say it is the defining Netbeans "feature" - if you Google any kind of Netbeans review this is the issue that is mentioned over and over again. I know Netbeans is free so we can't really complain, but because of this issue our company has recently switched to an alternative product - and from what I've read in forums I doubt we are alone.  It is sad because apart from this (pretty big!) problem the IDE really is a pleasure to use. :(
Comment 1 Jiri Prox 2016-03-17 17:20:46 UTC 
Can you please provide messages.log file from the run when the scanning was stuck? 

Also capturing several thread dumps when IDE is scanning too long may be usefull.

Thanks.
Comment 2 otisjenkins85 2016-03-18 11:18:16 UTC 
I had to reinstall the IDE in the end because I wasn't even able to rename files etc, and the issue seems to have gone away for now.

I wasn't aware of how to capture thread dumps, but the next time this happens (usually every few weeks or so) I will attach the dumps/logs etc.

Thanks!
Comment 3 otisjenkins85 2016-04-08 15:06:25 UTC 
OK this has started happening again.  Before I reinstall Netbeans (again!), how do I capture thread dumps so I can provide you with some useful data?

I still think if this is happening in EVERY VERSION of Netbeans I have ever had, on every machine I have ever had, and for this many people:

https://www.google.co.uk/search?q=netbeans+scanning 

then there must be something fundamentally wrong with the way it works? :(
Comment 4 Jiri Prox 2016-04-21 22:32:47 UTC 
Here is the guide how to capture threaddump.

It is not necessary to reinstall whole IDE, probably deleting cachedir will do.
Comment 5 allanford17 2017-08-11 02:13:58 UTC 
Having this issue also ... I will try uninstall and re-install ...
I did have Talend (Eclipse) open when I installed ... maybe not such a good idea to have other apps open when installing ..
Comment 6 allanford17 2017-08-11 02:31:11 UTC 
Maybe it is issue with "checking for external changes" ..
After re-install Netbeans worked for a little while.
Server may not have full open access to internet at work server.
Will post again if I work out solution to this issue.
Comment 7 mzav 2017-08-11 09:01:05 UTC 
IMHO the most probably it is related with GC. I've fixed problem for my very big project by increasing heap size for NetBeans:

netbeans_default_options="-J-client -J-Xss2m -J-Xms128m -J-Xmx6G -J-XX:MetaspaceSize=300m -J-Dapple.laf.useScreenMenuBar=true -J-Dapple.awt.graphics.UseQuartz=true -J-Dsun.java2d.noddraw=true -J-Dsun.java2d.dpiaware=true -J-Dsun.zip.disableMemoryMapping=true"

in NetBeans 8.2\etc\netbeans.conf