* Update globalmenu-extension to 3.1
- Reduce our memory footprint a bit, which wasn't really a lot anyway
- Avoid the use of the component manager for accessing commonly used
services, where "commonly used" means "accessed when building every
menu item". This should save some CPU cycles when building or
refreshing menus
- Try to recycle menuitems when they are removed from a menu by
adding contiguous blocks of removed items to a "free list" which
is emptied asynchronously, and reusing the items in this list when
new items are added in place of the removed items. This means that
menus which fully refresh on opening no longer alter the menu
structure, but instead just update properties on existing nodes.
This has a few benefits:
+ With no layout changes, unity-panel-service doesn't request
the entire menu structure, which significantly reduces dbus traffic
and makes it much faster to refresh the menu contents
+ The size of the menu doesn't change when it is refreshed, which
eliminates the flicker that used to occur when opening some menus
+ The HUD can refresh our menus now without triggering layout updates
(assuming that menu layout really hasn't changed)
- Remove all use of the global observer service for sending our own
internal notifications around
- Get rid of a static initializer
- Don't support older than Thunderbird 11
- Fix some GError leaks
- Hide the internal menu when creating a native menu, rather than
waiting for confirmation that the native menu is registered
successfully. We don't try to create a native menu if we don't
find a menu service to register the menu with anyway
- Keep menu contents updated whilst the menu is open, rather than
just whilst it is opening
-- Chris Coulson <email address hidden> Mon, 02 Apr 2012 17:52:31 +0100
This bug was fixed in the package thunderbird - 11.0.1+ build1- 0ubuntu1
--------------- build1- 0ubuntu1) precise; urgency=low
thunderbird (11.0.1+
* New upstream stable release (THUNDERBIRD_ 11_0_1_ BUILD1)
- Fixes LP: #962631, LP: #971578
* Update globalmenu- extension to 3.1
- Reduce our memory footprint a bit, which wasn't really a lot anyway
- Avoid the use of the component manager for accessing commonly used
services, where "commonly used" means "accessed when building every
menu item". This should save some CPU cycles when building or
refreshing menus
- Try to recycle menuitems when they are removed from a menu by
adding contiguous blocks of removed items to a "free list" which
is emptied asynchronously, and reusing the items in this list when
new items are added in place of the removed items. This means that
menus which fully refresh on opening no longer alter the menu
structure, but instead just update properties on existing nodes.
This has a few benefits:
+ With no layout changes, unity-panel-service doesn't request
the entire menu structure, which significantly reduces dbus traffic
and makes it much faster to refresh the menu contents
+ The size of the menu doesn't change when it is refreshed, which
eliminates the flicker that used to occur when opening some menus
+ The HUD can refresh our menus now without triggering layout updates
(assuming that menu layout really hasn't changed)
- Remove all use of the global observer service for sending our own
internal notifications around
- Get rid of a static initializer
- Don't support older than Thunderbird 11
- Fix some GError leaks
- Hide the internal menu when creating a native menu, rather than
waiting for confirmation that the native menu is registered
successfully. We don't try to create a native menu if we don't
find a menu service to register the menu with anyway
- Keep menu contents updated whilst the menu is open, rather than
just whilst it is opening
-- Chris Coulson <email address hidden> Mon, 02 Apr 2012 17:52:31 +0100