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.
While moving classes or renaming packages in a mid-size project I noticed bad refactoring performance. It took up to 10-15 minutes per single operation if the operations succeed at all. Occasionally the operations abort with an out-of-memory exception. After setting the NetBeans heap size to 768 mb (see below) the out-of-memory exceptions are gone but the bad performance still remains. The size of heap memory seems to have only small influence on the performance (expect when it comes to an exception). During the refactoring both cpu cores are used 100% until the operation is done. As a conclusion one can say that refactoring in NetBeans is unusable for me. Maybe you can have a look into my details a find the reason for this: 1. project facts number of classes: ~1160 number of projects: 6 (jpa, ejb, swing library, swing client and two util projects) 2. version systems facts product: subversion 1.5.4 (client and server) os: linux 3. my machine facts cpu: Intel Core2Duo T7300 @2.1 ghz memory: 2 gb swap file: 2 gb os: Windows XP SP3 4. java facts version: J2SE 1.6.0_07 5. netbeans facts version: NetBeans IDE 6.5 (Build 200811100001) Heap: -Xms768m -Xmx768m
*** This issue has been marked as a duplicate of 158360 ***