Hi Umut,


Thanks for the response. Regarding the limitation, yes, I misread an 
article to do with SQL Server and its XML component:
http://www.awprofessional.com/articles/article.asp?p=102307&seqNum=2&rl=1

The strange thing with this memory problem is that the system seems to 
indicate that only 1.5GB is used up until the DOM gives up and returns 
the E_OUTOFMEMORY error. Even if there was a leak, wouldn't the system 
start paging to disk? "Virtual memory"? Please correct me if I am wrong...


Regards,

Vivek



Umut Alev - MSFT wrote:
> Vivek,
> I am not sure where you got the 1/8th limitation info but there are no 
> such limits hard coded in msxml.
> If you see that you are running out of memory. Review your code and make 
> sure that you do not have any leaks in your code.
> Leaking user code is #1 culprit for these reports.
> 
> Regards,
> - Umut Alev [MSFT]
> 
> This email sent from a machine running Vista RC1.
> 
> "Vivek" <vivekd@o...> wrote in message 
> news:44f929dd$0$10627$afc38c87@n......
> 
>> Heya,
>>
>>
>> For large DOM documents (for XML documents that are required by the 
>> application to be persistently in the memory) MSXML6 is running out of 
>> memory and returning E_OUTOFMEMORY. From my brief research of this, I 
>> understand that MSXML6 DOM restricts itself to 1/8th of the physical 
>> memory (4GB on my system).
>>
>> Is there a way to allow MSXML6 to use more than 1/8th of the physical 
>> memory? Surely this can be toggled/configurable... Registry key? 
>> Parameter to the DOM? Documented/Undocumented?
>>
>>
>> Regards,
>>
>> Vivek 
> 
>