Apache OpenOffice (AOO) Bugzilla – Issue 20271
Q-PCD Performance-8 [Memory Usage]
Last modified: 2013-02-07 22:15:26 UTC
Source Many Category Memory usage Customer Need/Problem SO/OOo appears to use more memory than competing applications. Product Requirement SO/OOo should appear to use up as much memory on Windows as competing applications. Comment - Eng Effort - Eng Owner Matthias Huetsch Product Concept Partially addressed by concepts for ID Performance-1 (item 3) and ID Performance-4, but further improvements can be achieved in the following areas: 1) Further reduction of memory consumption as visible to a user can be achieved by requiring all on-demand loaded components to be disposable and to remove them from memory when no longer in use. 2) Further reduction of memory consumed for mass objects such as spreadsheet cells or drawing primitives can possibly be achieved by special purpose memory allocators that can store these objects more compact than a general purpose memory allocator can do. Further reduction of memory consumed during normal program use seems only possible through investigating individual cases where abnormal memory consumption is discovered. Functional Specification -
Accepting...
added keyword Q-PCD
One of the too much memory using parts is the spellchecker - especially when you use the functionality for suggesting the correct word. In such case the memory usage almost doubles!
according to the announcement on releases (http://www.openoffice.org/servlets/ReadMsg?list=releases&msgNo=7503) this issue will be re-targeted to OOo Later.
As explained in the initial description, memory usage issues will either be partly addressed by issue 20269 (Startup Performance) or they need individual investigation. Beyond that, remaining memory usage issues have been re-evaluated as being of a broader scope than anticipated, and have been re-prioritized in favor of other issues. They might be revisited on an individual base, or in a later release.
is this issue fixed ? as there is no activity since 2004 and since issue 20269 already fixed ? Thanks