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.
Steps to recreate issue. 1. Create a UML Project. 2. Add several hundred Classes to the UML Project. 3. Select all the Classes from Step 2 in the UML Project. 4. Right Click to display Pop-up menu. 5. The Pop-up menu (Step 4) takes several minutes to display. Note: I could understand a delay of several minutes once the Pop-up menu (Step 4) is displayed and the menu option "Create Diagram from Selected Elements" is selected when creating a diagram with several hundred Classes, but not when just trying to display a Pop-up menu.
using technics described at http://performance.netbeans.org/responsiveness/measuring/index.html for the current 5.5 build (i.e. "release55" branch) the comparative measurements (with Java project used as the baseline) were done as described below. Windows XP, jdk1.5.0_10, Intel Centrino Duo 2.33GHz, 2Gb RAM, IDE run with Xmx512m The measurements were done inside 2 projects: - Java Project for uml/core sources - UML Project created by reverse engineering the Java project on the nodes of the package org.netbeans.modules.uml.core.metamodel.core.foundation There are 140+ nodes in the package in both - Java as well as UML projects. The results are in milliseconds. Selecting all nodes in the package, no "Property" window open (see 84275 for related comments): Java : 391, 313, 344, 314 UML: 344, 360, 328 Selecting all nodes in the package, with "Property" window open: Java: 578, 500, 516 UML: 1593, 1453, 1438, 1422 Popup menu once all the nodes in the package are selected, no "Property" window open: Java: 687, 390, 406, 422 UML: 312, 203, 187, 172, 187 Popup menu once all the nodes in the package are selected, with "Property" window open: Java: 266, 328, 281, 312 UML: 460, 172, 187, 170, 219, 203 The measurements indicate that there is an issue with selecting of multiple nodes in the UML project when "Properties" window is open. (And so far the tentative fix already brings time decrease from ~1500 to ~1100 ms) The 84275 also mentiones this case. The measurements didn't show a problem with popup menu. Though it still looks possible that, due to asynchronous execution, the popup menu was delayed by the propety sets calculation caused by "Property" window, that delayed multiple-nodes selection in the measurements above.
As i haven't noticed the mentioned problem with pop-up menu once the nodes are selected and Property Sheet updated i close this bug as a duplicate of the 84275 "Terrible performance multi-selecting classes" (that bug also depends on 94321 which is a main reason for slow selection and pop-up menu coming up until property sheet re-calculated) *** This issue has been marked as a duplicate of 84275 ***
This has already been verified. Just verified again with selection of 55 packages and 530 elements, the popup menu came up with less than 1 second in delay.