[xml] Re: Memory leak in libxml

[pshankwar hss hns com]

Hi Daniel,
i used xmlCleanupParser() for memory clean up but core dump in following
area ( with purify and applicaiton in 64 bit).

            xmlFreeEntity
            xmlHashFree
            xmlCleanupPredefinedEntities
            xmlCleanupParser

Any Pointer for this

Thanks & Regds
Pradeep





Daniel Veillard <veillard redhat com> on 07/24/2003 05:23:52 PM

Please respond to veillard redhat com

To:    Pradeep Shankwar/HSS HSS
cc:

Subject:    Re: Memory leak in libxml


On Thu, Jul 24, 2003 at 12:18:48PM +0530, pshankwar hss hns com wrote:
> Hi,
> actually i am using the libxml version 2.2.11
>
> i wrote the following code which uses xmlParseMemory and xmlFreeDoc
> interface of libxml.
>
> {
>
> pDoc = xmlParseMemory(wml_c_text, size);
>
> if(pDoc != NULL)
>    {
>         ret = parse_document(pDoc, charset, &wbxml, all_cds);
>
>         wml_binary_output(*wml_binary, wbxml);
>
>          if (ret == -1)
>                printf("wml_compile: parse_document failed...\n");
>          else
>                    printf("wml_compile: length %d
\n",(*wml_binary)->len);
>     }
>     else
>     {
>             error(0,
>                 "WML compiler: Compiling error: "
>                 "libxml returned a NULL pointer");
>             ret = WBXML_ERROR;
>     }
>     wml_binary_destroy(wbxml);
>
>     if (pDoc)
>         xmlFreeDoc (pDoc);
>
>            }
>     }
>     else
>     {
>             error(0,
>                 "WML compiler: Compiling error: "
>                 "libxml returned a NULL pointer");
>             ret = WBXML_ERROR;
>     }
>     wml_binary_destroy(wbxml);
>
>     if (pDoc)
>         xmlFreeDoc (pDoc);
>
>     return ret;
> }
>
> But now i am getting 8byte memory leak in following code.
>                malloc
>                xmlStrndup
>                xmlAddEntity
>                xmlInitializePredefinedEntities
>                xmlInitParser
>                xmlParseDocument
>                xmlSAXParseMemory
>       xmlParseMemory.
>
> Is it a problem in the code or something wrong in libxml.

  What about reading the docs:
    http://xmlsoft.org/bug.html on how to report problem or get help
    http://xmlsoft.org/xmlmem.html on memory management
 or using the on-line search.The answer is "it's not a leak". Similar
questions
have been asked on the past, I have replied on the mailing list, they are
in the archive. I'm not interested in non-archived communication on the
topic, in part because I don't think repeating the same thing over and
over is a good use of my time.

> Waiting for ur reply
[...]
> "DISCLAIMER: This message is proprietary to Hughes Software Systems
Limited
> (HSS) and is intended solely for the use of the individual to whom it is
> addressed. It may contain  privileged or confidential information and
> should not be circulated or used for any purpose other than for what it
is
> intended. If you have received this message in error, please notify the
> originator immediately. If you are not the intended recipient, you are
> notified that you are strictly prohibited from using, copying, altering,
or
> disclosing the contents of this message. HSS accepts no responsibility
for
> loss or damage arising from the use of the information transmitted by
this
> email including damage from virus."

  I totally disagree to be bound by those terms for your unsollicited
message.
Ifyou want to get support from open-source developpers, removing this
sounds
like the very first thing to do, you cannot deny us the right to archive
and
make public communication based on a free support channel.

Daniel

--
Daniel Veillard      | Red Hat Network https://rhn.redhat.com/
veillard redhat com  | libxml GNOME XML XSLT toolkit  http://xmlsoft.org/
 http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/