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.
Product Version: NetBeans IDE Dev (Build 201705080001) Java: 1.8.0_131; Java HotSpot(TM) 64-Bit Server VM 25.131-b11 Runtime: Java(TM) SE Runtime Environment 1.8.0_131-b11 System: Windows 10 version 10.0 running on amd64; Cp1252; en_CA (nb) User directory: C:\Users\Gili\AppData\Roaming\NetBeans\dev Cache directory: C:\Users\Gili\AppData\Local\NetBeans\Cache\dev 1. Given a class that implements an interface where one of the methods is not implemented. 2. Begin to type the method name, then hit CTRL+SPACE to trigger auto-complete. 3. IDE will display "Please wait..." that will never go away. 4. If you abort code-complete and try again... over and over again... it'll take 10-15 seconds until you get actual search results instead of "Please wait..." 5. In past releases, results were available immediately most of the time. Expected behavior: * Results should be available immediately. * If they are not, "Please wait..." should display until results are ready. * Once results are ready, "Please wait..." should be replaced with the search results without the user having to close the pop-up and repeat the operation manually.
Unfortunately, I cannot reproduce the problem on my sources. Could you please create a profiler snapshot while waiting for code completion using the 'Profile the IDE action' (Alt+Shift+Y) and attach it to the issue? Thanks.
Created attachment 164332 [details] profiler snapshot I wasn't able to reproduce this issue with a minimal project, but I could easy get it on a larger project consisting of 4 Maven modules. I simply launched the IDE, waited for CPU usage to drop to 0%, then I invoked code-complete in one of the classes. I had "please wait..." for 10-20 seconds. Please review the attached snapshot.
I just reproduced the problem again and posted http://statistics.netbeans.org/analytics/exception.do?id=851141 The exception reporter is hinting that this issue might be a duplicate of bug #213907 but I don't see this problem in 8.2 final (meaning, this is a new regression for me). I have run 8.2 on multiple machines with no problems. By comparison, I have run multiple nightly builds that came out after 8.2 and they all have this problem.