[
https://issues.apache.org/jira/browse/XERCESC-2227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Scott Cantor updated XERCESC-2227:
----------------------------------
Issue Type: Bug (was: Improvement)
> 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
> Reporter: Even Rouault
> Assignee: Scott Cantor
> Priority: Major
>
> 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)
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org
For additional commands, e-mail: c-dev-h...@xerces.apache.org
