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.
This bug was originally marked as duplicate of bug 242126, that is already resolved. This bug is still valid, so this seems to be another bug, but it might be related. Build: NetBeans IDE Dev (Build 201408120001) VM: Java HotSpot(TM) 64-Bit Server VM, 24.55-b03, Java(TM) SE Runtime Environment, 1.7.0_55-b13 OS: Mac OS X User Comments: wanmifam: It lock the windows. Maximum slowness yet reported was 20237 ms, average is 20237
Created attachment 148667 [details] nps snapshot
Some ProxyLookup methods take several seconds to finish, please evaluate, thanks.
keeps on happening for me with 8.0 on macosx. I have to restart the IDE then and it works again for a few hours. Once the 20+ second delays start appearing, there's no other cure. Product Version: NetBeans IDE 8.0 (Build 201403101706) Updates: NetBeans IDE is updated to version NetBeans 8.0 Patch 2 Java: 1.7.0_60; Java HotSpot(TM) 64-Bit Server VM 24.60-b09 Runtime: Java(TM) SE Runtime Environment 1.7.0_60-b19 System: Mac OS X version 10.9.4 running on x86_64; UTF-8; en_US (nb) User directory: /Users/mkleint/Library/Application Support/NetBeans/8.0 Cache directory: /Users/mkleint/Library/Caches/NetBeans/8.0
If you looked at the invocation counts you would find out that while there is 28 invocations of org.openide.awt.ContextManager.isEnabled() there is then more than 700 of calls to org.openide.util.lookup.SimpleProxyLookup$ProxyResult.allItems() so I doubt the problem is in lookup. Just somebody calls into the lookup like crazy. There is a logging mechanism (since bug 223192) that should print the names of actions that are being re-computed. However it is only turned on when the IDE is executed with -ea as most of the reports is from 8.0, I am afraid we won't find the list. Anyone can simulate the problem with -ea on?
probably a dup of bug 242126
*** Bug 246627 has been marked as a duplicate of this bug. ***
apparently bug #242126 has not been fixed and the problem is elsewhere.
very likely caused by toooo many listeners being notified, see #250349
*** Bug 250458 has been marked as a duplicate of this bug. ***
*** Bug 250486 has been marked as a duplicate of this bug. ***
this issue is THE reason why I have to restart the IDE DAILY, sometimes multiple times! Is there anything I can do to help you track the problem? I'm using exclusively maven projects on git.
How can we/I help get enough information for this bug to be fixed? I have tried enabling -ea in my startup script as per Jaroslav Tulach's comment but no additional information related to this error appear.
(In reply to qte from comment #12) > How can we/I help get enough information for this bug to be fixed? > I have tried enabling -ea in my startup script as per Jaroslav Tulach's > comment but no additional information related to this error appear. When this happens please generate a heap dump, i think it's caused by #250349 - an OutOfMemoryError.
Created attachment 153635 [details] Thread dump using jstack
Created attachment 153636 [details] JMap histogram I have added both a memory histogram created using: map -histo:live <pid> And a thread dump created using jstack <pid> I can upload a full heap dump if required.
iterating over thousands of items in ProxyLookup.setLookups
Marking as fixed for now. See bug 250349 comment 13, which also applies to this issue. Thank you for reporting.