Hi Chris,
Am 24.11.2010 17:29, schrieb Chris Rider:
(Bump...)
We've been extensively testing opening/viewing PPT files, and have
noticed repeatable issues with memory not being cleared. These issues
appear when opening PPT files, ODP files, or even creating new ODP files.
We run CentOS 5.5, OOo 3.2.1
Do the following while monitoring resources (with like top)...
- Open OOo by running soffice
- Note base-level memory usage (in our test-case, 4-something MB)
- Open/Create presentation file (new, existing, PPT, ODP, etc. - any/all)
- Note memory again... (in our test case, 7.6MB)
All well and good up to this point now it gets interesting...
- Go to File - Close
- Note memory again... does NOT reduce!
Again, it didn't matter whether we created a new file, opened PPT,
opened ODP, etc whenever the file is closed, the peak memory use
remains. However, in these cases, completely closing soffice DID result
in the memory being cleared.
We first started investigating this while developing with document
server (and trying to figure out a memory leak there).
Closing a file and cleaning the memory should be at the forefront,
right? Is this by design? If a bug or memory leak, then it would be nice
to see it addressed in the new version coming out soon :)
Actually, there are quite some caches within the OOo code, with some of
them used cross-application. This means that even if all objects,
contained in one document and managed within the model code for the
document, get deleted correctly, there might remain some memory objects
in an soffice-wide cache.
In general this behavior occurs with graphis (pixel or vector graphics)
contained in a document, where the visual representation might still be
alive after closing a single document for sharing reasons.
The amount of memory used for this kind of cache can be adjusted by the
user via the 'Tools-Option-OOo-Memory' Tab Page. You could try to
reduce this default value to e.g. 0MB, in which case this cache won't be
used at all. But please be aware of the fact that rendering of graphics
and the responsiveness of the application might be worse with
such setting. So, please just use low cache values for testing purposes
only or if low memory is really an issue on your system.
With best regards
Kai
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.org
For additional commands, e-mail: dev-h...@openoffice.org
