Hi there,
I up-loaded the output of my string debug for a writer start:
http://www.gnome.org/~michael/llog.txt.gz
It ignores ref-counts, and shows real lifecycle data per string - ie.
how many times a copy of this string is allocated. I'll write a script
to crunch it in a bit & show what is actually kept, rather than being
transiently allocated then freed during startup.
Having said that, the top of the list shows no surprises:
$ zcat /tmp/llog.txt.gz | grep '^+' | sort | uniq -c | sort -n -r | head -n 10
39472 +IMPLEMENTATIONS
28446 +UNO
11297 +SERVICES
9618 +ACTIVATOR
4809 +PREFIX
4809 +LOCATION
3393 +en
2576 +
1589 +en-US
1539 +SINGLETONS
...
Then again - I was interested tat configmgr 'map' allocations are in
the top memory consumers, rather than string allocations; but - perhaps
that's down to some breakdown by size as well as by allocation site.
What's your estimate of the balance between strings and other types,
memory-wise ?
HTH,
Michael.
--
michael.meeks@suse.com <><, Pseudo Engineer, itinerant idiot
Context
- string / size bits ... · Michael Meeks
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.