Date: prev next · Thread: first prev next last
2012 Archives by date, by thread · List index


So, if you now run office under valgrind, i.e.

export VALGRIND=memcheck
./swriter

then if you kill -SIGUSR2 pid we get memcheck to dump out the backtraces
of active allocations, so can see where what memory we're using comes
from.

a) should add leak-check=full --show-reachable=yes to the valgrind line
in soffice to get full data, should probably add another option/env to
do that automatically for you)

b) only works if you've got a memcheck.h header that was auto-detected
during configure

My last-trace is available from
http://people.redhat.com/caolanm/trace/memcheck.active.allocs.log
that's just from an empty writer document

Two main things in there strike me. 
a) configuration data seems to occupy a lot of space
b) there are a lot of __static_initialization_and_destruction entries
where we over-use static rtl::OString or static rtl::OUString's which
all have to be initialized when their .so's are loaded and the
destructors for those registered to be called when they are unloaded.
Way too much churn noise for a few occasionally used strings.

C.


Context


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.