[jira] [Closed] (XERCESC-2227) Memleak fixes in ContentSpecNode and ComplexTypeInfo classes
"Scott Cantor (Jira)" <[email protected]>
| Newsgroups | gmane.text.xml.xerces-c.devel |
|---|---|
| Message-ID | <[email protected]> |
[ https://issues.apache.org/jira/browse/XERCESC-2227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Scott Cantor closed XERCESC-2227.
---------------------------------
> Memleak fixes in ContentSpecNode and ComplexTypeInfo classes
> ------------------------------------------------------------
>
> Key: XERCESC-2227
> URL: https://issues.apache.org/jira/browse/XERCESC-2227
> Project: Xerces-C++
> Issue Type: Bug
> Affects Versions: 3.2.3
> Reporter: Even Rouault
> Assignee: Scott Cantor
> Priority: Major
> Fix For: 4.0.0, 3.2.4
>
>
> 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.20.10#820010)