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 221699 - Slow code completion: macro expansion took 24301 ms
Summary: Slow code completion: macro expansion took 24301 ms
Status: NEW
Alias: None
Product: cnd
Classification: Unclassified
Component: Code Completion (show other bugs)
Version: 7.3
Hardware: All All
: P3 normal with 1 vote (vote)
Assignee: Vladimir Voskresensky
URL:
Keywords: PERFORMANCE
: 235966 241122 241123 (view as bug list)
Depends on:
Blocks:
 
Reported: 2012-11-08 09:32 UTC by Alexander Simon
Modified: 2015-09-25 17:09 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 194735


Attachments
nps snapshot (3.31 MB, application/nps)
2012-11-08 09:32 UTC, Alexander Simon
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Simon 2012-11-08 09:32:05 UTC
This issue was reported manually by alexvsimon.
It already has 1 duplicates 


Build: NetBeans IDE Dev (Build 20121108-4f7f1b7123ec)
VM: Java HotSpot(TM) Client VM, 20.8-b03, Java(TM) SE Runtime Environment, 1.6.0_33-b03
OS: SunOS
Maximum slowness yet reported was 24301 ms, average is 24301
Comment 1 Alexander Simon 2012-11-08 09:32:45 UTC
Created attachment 127368 [details]
nps snapshot
Comment 2 Vladimir Kvashin 2012-12-07 08:38:12 UTC
Snapshot shows that 3/4 time is in extremely deep recursive calls of two methods calling each other:
  MacroExpandedToken.getText
  APTMacroExpansion.getText
  MacroExpandedToken.getText
  APTMacroExpansion.getText
  ...
And about 18% is in 
  APTUtils.getExpandedToken which goes into a very deep recursion
Comment 3 Vladimir Voskresensky 2014-02-10 15:38:37 UTC
*** Bug 241123 has been marked as a duplicate of this bug. ***
Comment 4 Vladimir Voskresensky 2014-02-10 15:38:59 UTC
*** Bug 241122 has been marked as a duplicate of this bug. ***
Comment 5 Vladimir Voskresensky 2014-02-10 15:53:14 UTC
*** Bug 235966 has been marked as a duplicate of this bug. ***