You are viewing a plain text version of this content. The canonical link for it is here.

Posted to c-dev@xerces.apache.org by "Even Rouault (Jira)" <xe...@xml.apache.org> on 2021/09/22 20:10:00 UTC

[jira] [Created] (XERCESC-2227) Memleak fixes in ContentSpecNode and ComplexTypeInfo classes

Even Rouault created XERCESC-2227:
-------------------------------------

             Summary: Memleak fixes in ContentSpecNode and ComplexTypeInfo classes
                 Key: XERCESC-2227
                 URL: https://issues.apache.org/jira/browse/XERCESC-2227
             Project: Xerces-C++
          Issue Type: Improvement
            Reporter: Even Rouault


when a OutOfMemory exception occurs.

Spotted by [https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=39127] (on GDAL)

The commits are a bit in increasing order of triviality. The ownership rules of ContentSpecNode first and second members, as used by ComplexTypeInfo, are super complex. shared_ptr would be much welcome here! I can just tell that valgrind on my test case reports no double-free nor memory leak after those fixes....



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org