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.

Bug 147015 - JAVA performance degradation after multiple "Change Variable Name" operations
Summary: JAVA performance degradation after multiple "Change Variable Name" operations
Status: RESOLVED DUPLICATE of bug 124777
Alias: None
Product: guibuilder
Classification: Unclassified
Component: Code (show other bugs)
Version: 6.x
Hardware: PC Windows XP
: P3 blocker (vote)
Assignee: issues@guibuilder
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-09-12 01:32 UTC by jerryschreiber
Modified: 2008-09-12 06:30 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description jerryschreiber 2008-09-12 01:32:52 UTC
I am developing a JFrame with a large number of JButtons (grouped on JTabbedPanes, 8 tabs each with 16 buttons).   In
the process of using "Change Variable Name" to set application-relevant names to the JButtons, the CPU of the java.exe
process goes up to 100% (as measured with Windows Task Manager).   For the first few, the CPU does come back down
relatively quickly (10 sec or less), but after 15 or so, the time during which the CPU remains at 100% gets longer and
longer, exceeding 30 sec.

I notice that, once it's reached this state, after I shut down NetBeans, Java.exe remains above 90% (I waited > 60 sec),
until I kill the process with Task Manager.
Comment 1 Jan Stola 2008-09-12 06:30:34 UTC

*** This issue has been marked as a duplicate of 124777 ***