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 "Scott Cantor (JIRA)" <xe...@xml.apache.org> on 2017/07/12 23:23:00 UTC
[jira] [Updated] (XERCESC-1350) DTDElementDecl lazy initialization
not thread safe.
[ https://issues.apache.org/jira/browse/XERCESC-1350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Scott Cantor updated XERCESC-1350:
----------------------------------
Affects Version/s: 3.2.0
3.0.0
3.1.0
3.1.1
3.1.2
3.1.3
3.1.4
> DTDElementDecl lazy initialization not thread safe.
> ---------------------------------------------------
>
> Key: XERCESC-1350
> URL: https://issues.apache.org/jira/browse/XERCESC-1350
> Project: Xerces-C++
> Issue Type: Bug
> Components: Validating Parser (DTD)
> Affects Versions: 3.0.0, 3.0.1, 3.1.0, 3.1.1, 3.1.2, 3.2.0, 3.1.3, 3.1.4
> Environment: Solaris
> Reporter: Mark Weissman
>
> DTDElementDecl.cpp && DTDElementDecl.hpp perform lazy evaluation on many
> of the get() methods. This is used in cached grammars which may
> be shared by multiple threads and accessed unsynchonized.
> Lazy initialization is generally a bad pattern, but particularly in multithreaded
> applications. It should be disabled for shared grammars.
> I work around this by calling all the getters when I create my Grammar pool
> but I think this should not be necessary.
> It would be good if somebody could check all the lazy evaluations that might
> affect shared grammars.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org