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 GitBox <gi...@apache.org> on 2021/12/04 19:16:43 UTC
[GitHub] [xerces-c] rleigh-codelibre commented on a change in pull request #44: [XERCESC-2233] DFAContentModel::buildDFA(): fix memory leaks when OutOfMemoryException occurs
rleigh-codelibre commented on a change in pull request #44:
URL: https://github.com/apache/xerces-c/pull/44#discussion_r762456999
##########
File path: src/xercesc/validators/common/DFAContentModel.cpp
##########
@@ -1191,12 +1203,21 @@ void DFAContentModel::buildDFA(ContentSpecNode* const curNode)
// table.
//
statesToDo[curState] = newSet;
- fTransTable[curState] = makeDefStateList();
- stateTable->put
- (
- newSet
- , new (fMemoryManager) XMLInteger(curState)
- );
+ try
+ {
+ fTransTable[curState] = makeDefStateList();
+ stateTable->put
+ (
+ newSet
+ , new (fMemoryManager) XMLInteger(curState)
+ );
+ }
+ catch( const OutOfMemoryException& e )
+ {
+ oomException = e;
Review comment:
How safe is the saving and re-throwing of the exception? Is there any potential for `OutOfMemoryException& e` to be a reference to a base class? Could `e` end up being truncated as a result? A direct `throw` to rethrow the existing exception might be safer overall, and avoid the need for a goto.
Could we achieve the same effect with a higher-level try/catch block within the function, and avoid the saving of the exception and the goto?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org