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 174050, that is already resolved. This bug is still valid, so this seems to be another bug, but it might be related. Build: NetBeans IDE 7.0.1 (Build 201107282000) VM: Java HotSpot(TM) Client VM, 20.1-b02, Java(TM) SE Runtime Environment, 1.6.0_26-b03 OS: Windows Vista User Comments: ojitos86: the system keeps wanting to "check for external changes" which is great and all but the entire programs freezes for about 3 mins every 10-15mins checking for theses external changes... I have been useing this program for about a year now with now problems but as of yesterday after updateing the system it has not been working. please help Maximum slowness yet reported was 46123 ms, average is 46123
Created attachment 110760 [details] nps snapshot
Tomáši, this snapshot takes really long to open and eats 500MB of memory. Yet it seems to last only for 35s. Maybe you want to investigate.
The stacktraces shows tons of recursive calls to: org.netbeans.modules.masterfs.filebasedfs.fileobjects.FolderObj.hasRecursiveListener() in the Refresh-After-WindowActivated thread. No wonder the npss took so long to process. It seems that we have traded the I/O access for a heavy CPU computation to eliminate it.
(In reply to comment #2) > Tomáši, this snapshot takes really long to open and eats 500MB of memory. Yet > it seems to last only for 35s. Maybe you want to investigate. ok, I will take a look.
There are stacktraces with more than 1500 frames. To lower the memory consumption, ObjectOutputStream is reset every 5000 samples. Maybe we should also consider number of stack frames in samples and reset ObjectOutputStream more frequently.
There is just one report from 7.1 (beta): http://statistics.netbeans.org/exceptions/exception.do?id=543021 It shows 11s being wasted in java.io.File.isDirectory() 100.0 11469 ms (100%) 11469 ms java.io.WinNTFileSystem.getBooleanAttributes[native]() 100.0 11469 ms (100%) 11469 ms 1 I don't think three is any need to fix this.