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


Hello,

Scan coverity detected this:
Resource leak in object (CTOR_DTOR_LEAK)1. alloc_fn: Calling allocation
function "osl_createCondition()". [show details]
(see
http://opengrok.libreoffice.org/xref/core/filter/source/xsltfilter/XSLTFilter.cxx#164)

osl_createCondition in unx part calls a malloc function  (see
http://opengrok.libreoffice.org/xref/core/sal/osl/unx/conditn.cxx#43)
and osl_destroyCondition frees the element (see
http://opengrok.libreoffice.org/xref/core/sal/osl/unx/conditn.cxx#92)

First I thought about adding a destructor for "XSLTFilter" which would just
call "osl_destroyCondition"
but then I noticed the class "XSLTFilter" which inherits from
"WeakImplHelper4" which itself inherits from "OWeakObject"
Finally I must recognize I don't know if these classes do the trick to free
the memory or if a destructor in "XSLTFilter"  is relevant.

Any idea?

Julien



--
View this message in context: 
http://nabble.documentfoundation.org/About-coverity-704144-XSLTFilter-tp4043364.html
Sent from the Dev mailing list archive at Nabble.com.

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.