So, after clearing up a pile of circular ownership things to clear out
deadwood blocking valgrind from telling me what I wanted to know I
tracked down a a leak in framework/source/services/frame.cxx where for
each frame we do a new WindowCommandDispatch, and the comment claims
that the WindowCommandDispatch will release itself at frame destruction.
It doesn't of course, its implemented as a uno XEventListener but
doesn't register itself as a uno listener to the frame to even have a
chance of doing the right thing. It itself registers itself as a vcl
listener to the frame, and doesn't delete itself on OBJ_DYING.
So, I could remove the XEventListener foo, add a delete this on
OBJ_DYING to remove the leak.
My open question though, is it that this WindowCommandDispatch exists
apparently do bind some mac "About" and "Preferences" events to do the
right thing on that platform. What's special about About/Preferences in
Mac ?, and does it currently work correctly ?, i.e. its worth fixing
this rather than removing it entirely.
C.
Context
- [Libreoffice] leak per frame, mac input request. · Caolán McNamara
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.