[ 
https://issues.apache.org/jira/browse/XERCESC-2019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13818089#comment-13818089
 ] 

Alberto Massari commented on XERCESC-2019:
------------------------------------------

There is the limitation of the memory required to keep the data in memory; 
there is the overhead of the DOM nodes, and the data of the XML is kept in 
Unicode format, so assuming your XML is almost entirely a single text node, at 
a certain point you could have allocated the 179Mb*sizeof(XMLCh) of the 
previous buffer plus a 2*179Mb*sizeof(XMLCh) new buffer, that is more than 1Gb 
of memory

> Error in memory allocation for even small messages.
> ---------------------------------------------------
>
>                 Key: XERCESC-2019
>                 URL: https://issues.apache.org/jira/browse/XERCESC-2019
>             Project: Xerces-C++
>          Issue Type: Bug
>          Components: DOM
>    Affects Versions: 3.1.1
>         Environment: windows XP vc9, linux and solaris
>            Reporter: mahalakshmi
>            Assignee: Alberto Massari
>              Labels: patch
>             Fix For: 3.2.0
>
>         Attachments: zippedfiles.zip
>
>
> I have my xsd schema using which i have created my standard xml.
> After creating the xml i fill the values for each tag in my xml. 
> I get memory allocation error when i try to traverse through the xml and set 
> the values for each tag in my xml.
> I get allocation error when my program calls the setTextcontent() of 
> xerces.It is crashing in DOMDocumentImpl.cpp allocate(size).(2nd if condition 
> in that function)
> Is there any setting that needs to be done for memory allocation? How much is 
> the maximum size of xml that xerces can parse?how do we manage the memory 
> allocation and deallocation in DOM?



--
This message was sent by Atlassian JIRA
(v6.1#6144)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to