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 232939, that is already resolved. This bug is still valid, so this seems to be another bug, but it might be related. Build: NetBeans IDE 8.0 Beta (Build 201401141042) VM: OpenJDK 64-Bit Server VM, 24.45-b08, OpenJDK Runtime Environment, 1.7.0_51-b00 OS: Linux User Comments: GUEST: Updating composer dependencies in a PHP project and going through the options Maximum slowness yet reported was 3831 ms, average is 3831
Created attachment 144759 [details] nps snapshot
I think there is a general consensus we won't do anything with slow classloading (due to overloaded disk). The http://statistics.netbeans.org/exceptions/exception.do?id=710400 report is an example of such case: - more than 3s spend under ProxyClassLoader - there is just one call to ProxyClassLoader I know we do various detections to eliminate broken snapshots. Could we also add a "classloading check"? If at least 90% of time is spend in a single call to org.netbeans.*ClassLoader, consider the report broken and don't promote it to the server?
Such testing cannot be done in NetBeans itself. We can do it on the statistics.netbeans.org server, where we have proper infrastructure - it can be similar to Slow Windows I/O test.
*** Bug 237231 has been marked as a duplicate of this bug. ***