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.
Created attachment 154984 [details] current log. From time to time, after making big changes, or changing the "main project", the background scanning of projects hangs. Currently its been showing 6% with 23 more. The attached log is not showing anything (I think). I can leave it like this for the next hour or two... could you tell me how to capture whatever is hanging? This could be a dup of #207991, but that was marked fixed long ago. Product Version: NetBeans IDE Dev (Build 201507280002) Updates: Updates available Java: 1.8.0_45; Java HotSpot(TM) 64-Bit Server VM 25.45-b02 Runtime: Java(TM) SE Runtime Environment 1.8.0_45-b14 System: Linux version 3.14.27-100.fc19.x86_64 running on amd64; UTF-8; en_US (nb) User directory: /home/toddb/.netbeans/dev Cache directory: /home/toddb/.cache/netbeans/dev
Created attachment 154988 [details] updated log Gave up waiting, but closing the ide introduces a new hang, with a few interesting lines in the attached log.
cnd project please investigate, the second log shows a lot of cnd threads just waiting.
very strange huge amount of "Open/Close project ..." activity together with "Code Completion: scheduleParsing..."
Todd when you said scanning what was the name of task in progress? "Scanning" or "Parsing"?
"scanning...", I'm sure of it.
Is there something I could capture next time this occurs. Has not happened since I filed this yesterday. Maybe a few times per week.
If you have seen "scanning..." then I think the reason is: you switched between IDE and other application, then back to IDE. IDE assume that you might touch some files while been out of IDE context (i.e. from your command line). So, when you move focus back to IDE it starts Thread id 150, "Refresh-After-WindowActivated" and checks all source roots. But in your case smth happened with locks. So, the next time you see that scanning progress which doesn't move forward, please, take threads dump.
Todd, Were you able to see the issue and take threads dump? Thanks, Vladimir.
No. Sorry. It may have been fixed in a later build. I am currently running 20150823.