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 40273 - First invocation of context menu in XML text editor is slow
Summary: First invocation of context menu in XML text editor is slow
Status: VERIFIED FIXED
Alias: None
Product: xml
Classification: Unclassified
Component: Text-Edit (show other bugs)
Version: 3.x
Hardware: PC All
: P3 blocker (vote)
Assignee: Petr Pisl
URL:
Keywords: PERFORMANCE
Depends on:
Blocks:
 
Reported: 2004-02-19 13:17 UTC by _ rkubacki
Modified: 2007-09-25 01:33 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
List of classes loaded when opening the editor popup menu (3.04 KB, text/plain)
2004-02-23 14:29 UTC, Petr Jiricka 		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-02-19 13:17:34 UTC 
It should be within 100 ms but current results are
above 200 ms.

The numbers are bad even in our test suite where
many other menus is measured before context menu
is XML text editor (including main menu, context
menu on nodes of various types, popup in Java editor).

results from 200402181900 on Linux, Solaris, WinXP.

XML Editor popup (1)  141 ms (+61.7%)  180 ms
(+27.2%)  125 ms (+74.1%)
Comment 1 Petr Pisl 2004-02-19 16:48:34 UTC 
The actions are defined through the layer, so the editor module
construct the context menu. Could you give me more information? Can
you measure individual items in the menu?
Comment 2 Petr Jiricka 2004-02-23 14:26:17 UTC 
Attaching the list of classes loaded when opening the popup menu in
the XML editor. Radim, can you please estimate how long this loading
takes?
Comment 3 Petr Jiricka 2004-02-23 14:29:26 UTC 
Created attachment 13574 [details]
List of classes loaded when opening the editor popup menu
Comment 4 Martin Schovanek 2004-02-25 10:53:34 UTC 
I agree that performance is important for us. But in my opinion it is a bit
risky make a code optimization to promo-B now. This case does not affect users
too much. That's why I (XML QE) propose to postpone the bugfix.
Comment 5 Petr Jiricka 2004-02-27 09:29:12 UTC 
This is improved by the fix that Radim did for issue 40271, so marking
as fixed.
Comment 6 Antonin Nebuzelsky 2004-03-11 10:14:47 UTC 
This bug should be either closed as fixed or retargetted for promo-D
if there is still something we can/want to do to improve it.
Comment 7 _ pkuzel 2005-02-21 13:42:02 UTC 
Have not hard measured but it looks slick and snappy.
Comment 8 Mikhail Matveev 2007-09-21 13:30:08 UTC 
Verified - fixed a long time ago, seem to work quickly enough now