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 issue was reported manually by mmirilovic. It already has 60 duplicates Build: NetBeans IDE Dev (Build 201204100400) VM: Java HotSpot(TM) Client VM, 20.6-b01, Java(TM) SE Runtime Environment, 1.6.0_31-b05 OS: Windows XP User Comments: GUEST: The properties doesn't work! When I click on it, it just disappears. This netbeans(6.9.1) runs on a windows xp. GUEST: Doing tutorial on this : http://platform.netbeans.org/tutorials/nbm-projecttype.html On step 2, in Setting dependencies, I found everything except Project/Project UI API, so I move to my RCP module suite and left click on its node and select Properties. Nothing appears for a while, then the Project Properties window appears as well as the slowness icon on the bottom left. jtulach: I just right clicked on my suite project quyvle: Running on Windows 7. Netbeans runs really slowly. Lags interminently for lengths at a time. Performance is poor compared to the Eclipse IDE. musilt2: during creating new NB platform app in wizard javydreamercsw: Closing a Module project GUEST: opening netbeans and this problem is occured jtulach: Suite's Branding jglick: Switching NB platform in new suite wiz. lanthale: Just right click on my RCP application and selected "Properties". GregoryTechSoft: Slowness detected after uninstalling third-party modules, re-starting IDE, and opening a module suite project of the modules which were previously uninstalled. I presume the actual module suite I am working with is unimportant; but in any case, the actual module suite is my own personal adaptation of the flexbean suite, that I've been trying to use for editing a Flash/Flex project with lots of ActionScript files + miscellaneous resources. jglick: Starting "Options Panel" wiz on ant.browsetask module. javydreamercsw: Loading module dependencies (Module Properties>Libraires) arittner: Starting NetBeans IDE with new JDK7 (64bit) and a whole bunch of projects Lolo_101: Entered some text in the plugins "search" text field GUEST: After choosing Eclipse workspace, loading screen to choose project to import jtulach: 16s in waiting for suite's properties gorrus: deleted NB platform zolta: closing project krissco: Soon after IDE opening, I took a look at Tools/Netbeans Platforms. The slowness could have been scanning the open projects at startup (eight open projects) or may have been related to the Platform Manager window. azizur: Started the IDE after OS restart vieiro: This is simply unusable. jocke: ... GUEST: jsf Maximum slowness yet reported was 44129 ms, average is 14567
Created attachment 120693 [details] nps snapshot
reassign to performance for evaluation
it seems org.netbeans.modules.autoupdate.services.Utilities.getModuleConfiguration is trying to get configuration from xml consequently most of the time is spent in java.io.FileInputStream.readBytes seems like another slow filesystem issue, but to make sure, autoupdate guys please take a look at this.
(In reply to comment #3) > it seems > org.netbeans.modules.autoupdate.services.Utilities.getModuleConfiguration is > trying to get configuration from xml consequently most of the time is spent in > java.io.FileInputStream.readBytes > > seems like another slow filesystem issue, but to make sure, autoupdate guys > please take a look at this. I don't see any problem in code that could cause this slowness. I have to evaluate it and confirm Petr's opinion as filesystem issue.
lfischmeistr, Petr evaluated snapshot and pointed out that slow I/O was done in EDT. According to 7.2 goals it has to be fixed, not resolved as 'wontfix'
Dear Vladimir, Let me treat you two some beer and tapas if you ever happen to visit Spain. Kind regards, Antonio
It's a pellmell issue. Almost each snapshot leads to different component. I assiging back to performance.
(In reply to comment #3) > it seems > org.netbeans.modules.autoupdate.services.Utilities.getModuleConfiguration is > trying to get configuration from xml consequently most of the time is spent in > java.io.FileInputStream.readBytes I see. On user action (applying filter in Available plugins in Plugin Manager), metadata of all plugins has to be scanned. I agree it should be call on background and UI just show a wait cursor in the meantime. > seems like another slow filesystem issue, but to make sure, autoupdate guys > please take a look at this.
we should be concerned only about the latest two reports - all the others are too old to matter and the lack of duplicates for them signifies that the problem was likely resolved.
This is the stopper for NB 7.2, please evaluate and resolve ASAP.
just to be clear I have split off the second "recent" exception report, so the only one which should be fixed is : http://statistics.netbeans.org/exceptions/exception.do?id=573304 - the issue with org.netbeans.modules.autoupdate.services.Utilities.getModuleConfiguration