[jira] Updated: (XERCESC-1051) Crash when maxOccurs = 200000

[ https://issues.apache.org/jira/browse/XERCESC-1051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Boris Kolpackov updated XERCESC-1051: - Fix Version/s: 3.0.0 Tentatively changing the fix for version to 3.0.0. Alberto has a

API changes to transcoding service for more explicit use of MemoryManager

Hi, I discovered a bug in the IconvGNUWrapper yesterday where a Mutex was being default constructed with the global MemoryManager instance. In trying to fix it, I noticed that explicit memory management was never pushed into the APIs, because we didn't want to break everything in the 2.x

[jira] Commented: (XERCESC-1051) Crash when maxOccurs = 200000

[ https://issues.apache.org/jira/browse/XERCESC-1051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12596465#action_12596465 ] Michael Glavassevich commented on XERCESC-1051: --- You may want to take a

Re: API changes to transcoding service for more explicit use of MemoryManager

Hi David, David Bertoni [EMAIL PROTECTED] writes: Are there any objections if I make some API changes that will result in explicit use of the MemoryManager class when creating a transcoding service and creating transcoders? Is it not possible to make the choice default to the global memory