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





------- Additional comments from [EMAIL PROTECTED] Fri Aug 25 06:39:53 -0700 
2006 -------
>From a memory consumption standpoint the considerable savings achieved by the
changes are just small potatoes though when compared to libfontconfig or
libfreetype allocations. The massif tool reports them as top scorers:

Heap allocation functions accounted for 84.5% of measured spacetime
Called from:
  21.5% : 0x72325F1: FcPatternFreeze (in /usr/lib/libfontconfig.so.1.0.4)
   9.0% : 0x72327CE: FcPatternFreeze (in /usr/lib/libfontconfig.so.1.0.4)
   8.8% : 0x72313B5: FcObjectStaticName (in /usr/lib/libfontconfig.so.1.0.4)
   7.0% : 0x5470D3C: (within /usr/lib/libfreetype.so.6.3.10)
   5.3% : 0x7226BCA: (within /usr/lib/libfontconfig.so.1.0.4)
   4.0% : 0x40084A3: (within /lib/ld-2.3.6.so)
   2.7% : 0x4D14AC4: osl_createMutex (in libuno_sal.so.3.1.1)
   2.3% : 0x7226D24: (within /usr/lib/libfontconfig.so.1.0.4)
   1.7% : 0x4F26B83: XOpenDisplay (in /usr/lib/libX11.so.6.2.0)
   1.7% : 0xA385874: (within libpackage2.so.1.1)
   1.4% : 0x4F278A3: XOpenDisplay (in /usr/lib/libX11.so.6.2.0)
   1.4% : 0x777289E: _XimParseStringFile (in
/usr/lib/X11/locale/common/ximcp.so.2.0.0)
   1.3% : 0x7232912: FcStrCopy (in /usr/lib/libfontconfig.so.1.0.4)
   0.9% : 0x4F3A71E: _XEnq (in /usr/lib/libX11.so.6.2.0)
   ...

---------------------------------------------------------------------
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