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 43289 - [refactoring] [perf] Modifying source files after find usages triggers heavy CPU activity
Summary: [refactoring] [perf] Modifying source files after find usages triggers heavy ...
Status: CLOSED FIXED
Alias: None
Product: editor
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 4.x
Hardware: PC Linux
: P2 blocker (vote)
Assignee: issues@java
URL:
Keywords: PERFORMANCE
Depends on:
Blocks:
 
Reported: 2004-05-14 16:55 UTC by _ rkubacki
Modified: 2007-11-05 13:44 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Full Thread Dump (18.13 KB, text/plain)
2004-05-18 10:26 UTC, Jan Becicka 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description _ rkubacki 2004-05-14 16:55:01 UTC 
refactoring build from May 13, jdk1.5.0b50, Linux

perform find usages and go to some source with
found occurence and modify it - several seconds of
CPU activity are common case before editor becomes
responsive again and all found results are lost.
Comment 1 Jan Becicka 2004-05-18 10:25:56 UTC 
A did a thread dump, while IDE frozed for a while and there is
suspicious editor stuff:
JavaIndentEngine.createFormatter(JavaIndentEngine.java:53) causes
ClassLoader to load classes in AWT event queue. Is that correct?

Reassigning to editor for further evaluation.

Note:
Fact, that found result get lost is correct.
Comment 2 Jan Becicka 2004-05-18 10:26:54 UTC 
Created attachment 14932 [details]
Full Thread Dump
Comment 3 _ rkubacki 2004-05-18 10:41:43 UTC 
Simple way to check when/what classes are loaded is to add
-J-verbose:class option to the IDE command line

re losing results: it might be correct according to some spec. Anyway
IMO this is a wrong model. It is not helpful.
Comment 4 Jan Becicka 2004-05-18 10:49:49 UTC 
re: -J-verbose
Thanks! :)

re: losing results:
It is correct IMHO. When you modify source, found results become
obsolate and thus disappear.
I admit, that results can stay visible for Find Usages. But it
definitely must disappear for refactoring preview. Unfortunately from
implementation point of view, there is almost no difference between
find useges and refactoring preview.
Comment 5 Martin Matula 2004-05-18 10:58:34 UTC 
re lost results: You can always click on the refresh button in the
Where Used panel toolbar.
Comment 6 Martin Matula 2004-06-19 22:49:25 UTC 
Does not seem to occur since we fixed the usages so that they are not
lost.
Comment 7 Roman Strobl 2005-07-14 16:46:58 UTC 
Radime, can you please verify this issue? Thanks.
Comment 8 _ rkubacki 2005-07-14 17:49:27 UTC 
v