To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=84550





------- Additional comments from [EMAIL PROTECTED] Wed Feb 20 10:36:08 +0000 
2008 -------
To make my above-mentioned confidence somewhat more concrete, I played a little
bit ...

- fresh OOo 2.4 RC1
=> menus (from the menu bar) open fine, context menus in Writer open fine, no
   performance problems
- installed LanguageTool 0.9.1 (the extension originally mentioned in
  this issue, a ZIP package), restarted OOo
=> menus are slooooow to open, a context menu in Writer takes a lot of seconds
   to open, application is hung meanwhile
- de-installed the LanguageTool extension, restarted OOo
=> performance is back to normal level
- re-installed the extension
- changed the implementation of DataBaseIterator::nextDb to not look for
  help in the shared and user extensions
=> context/menu performance is absolutely fine

Debugged this a little. What happens when a context/menu is opened is a call to
GetHelpAnchor_Impl in sfx2/source/appl/sfxhelp.cxx. There, a UCB content is
created for the given help URL, and then asked for its AnchorName property. And
somewhere within this call getPropertyValue( "AnchorName" "), the help backend
decides to scan all extension packages.

So, I am *really* confident that a caching mechanism, which caches the
information whether a given package actually contains help content or not, will
resolve all performance issues: main menus, context menus, Calc behavior. And
more, probably.

(Note that I think more optimization can and probably should be done later. For
instance, it is not really arguable why asking a given UCB content, which refers
to an existing help topic in the base installation, needs to scan the
extension's help when being asked for a AnchorName property. However, this
should be a different fix, to be on the safe side for 2.4.)

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to