![]() |
![]() | ![]() | ![]() | Altova Mailing List Archives>Archive Index >microsoft.public.xml Archive Home >Recent entries >Thread Prev - Re: IXMLDOMNode - get_xml limitation? [Thread Next] Re: IXMLDOMNode - get_xml limitation?To: NULL Date: 9/2/2006 5:12:00 AM 1. IXMLDOMNode::get_xml method is returning a BSTR. 2. Are you running under x86 or x64? Usually x86 can only see upto 2GB after that you need to turn on /3G flag. 3. to access full 4GB you need to switch to x64. -- Regards, - Umut Alev [MSFT] This email sent from a machine running Vista RC1. "Anthony Jones" <Ant@y...> wrote in message news:eZ9TYV3yGHA.4576@T...... > > "Vivek" <vivekd@o...> wrote in message > news:44f43bcb$0$25358$afc38c87@n...... >> Hi Anthony, >> >> >> Here is the example: >> >> --- >> HRESULT hr; >> CComBSTR testString; >> hr = GetNodePtr()->get_xml(&textString); >> unsigned int strLength = textString.Length(); >> --- >> >> Actually, I tried it again now, and I got hr = E_OUTOFMEMORY, rather >> than hr = S_OK like last time. I have 4GB of physical memory on this >> system and it seems have to only used up 1.5GB (the application that >> instantiates the DOM alltogether). >> >> Is there a way to allow MSXML6 to use more memory? >> > > I doubt it. XML is not a technology really expecting this sort of size of > data (at least not held as a DOM all at one time). The amount of data > involved really indicates that some sort of indexed file system ought to > be > used instead for persisting and querying this data. > > Despite having 4GB of memory by default the user mode memory map is only > 2GB > and everything in the process that isn't shared with other processes has > to > be held in it. It would appear that you are running out of this memory. > > > >> More info: >> --------- >> &textString is now <Bad Ptr> >> strLength = 0 >> GetNodePtr() is of type: "IXMLDOMNode *<Class>::GetNodePtr(void) const" >> >> >> Regards, >> >> Vivek >> >> Anthony Jones wrote: >> > "Vivek" <vivekd@o...> wrote in message >> > news:44f42dbd$0$22363$afc38c87@n...... >> > >> >>I forgot to mention that I am using the IXMLDOMNode object in C++ and >> >>nodes that are not too big (< 200MB) seem to be fine, but anything >> >>beyond 200MB seem to return as empty strings! Any explanation for why >> >>this might be occuring? >> >> >> >> >> > >> > >> > Can you show a code snippet of how it is called? >> > >> > What is the value of the returned HRESULT? Is it S_OK? >> > >> > >> > >> > >> >>Regards, >> >> >> >>Vivek >> >> >> >>Vivek wrote: >> >> >> >>>When I am attempting to retrieve the contents of a very large node in >> >>>a >> >>>DOM document with the get_xml(BSTR *xmlString) member function, the >> >>>pointer is leading to am empty string. >> >>> >> >>>Is there a documented limitation of how large a particular node in >> >>>MSXML6 can be? I've searched on MSDN and the MSXML6 SDK without any >> >>>success... >> >>> >> >>>If a Microsoft support representative can respond to this, then that >> >>>would be great. >> >>> >> >>> >> >>>Regards, >> >>> >> >>>Vivek >> > >> > >> > > > | ![]() | ![]() | ![]() |
| Company | Legal | Press | Partners | Careers | Sitemap | Contact Us | Altova Blog | |||||
|
