Re: Newbie: CComBSTR limitation?

From:

"Alexander Nickolov" <agnickolov@mvps.org>

Newsgroups:

microsoft.public.vc.atl

Date:

Wed, 13 Sep 2006 21:25:33 -0700

Message-ID:

<ujVwrX71GHA.2516@TK2MSFTNGP06.phx.gbl>

Actually, the physical memory is not a limit - the virtual address
space is the limit, or rather how it's fragmented. So even though
in theory you could allocate up to 2GB memory, in practice
the data shares the address space with the code, and there
are several heaps competing for the available virtual addresses.
If you need larger data chunks than what you get, I suggest you
consider moving to Win64.

--
=====================================
Alexander Nickolov
Microsoft MVP [VC], MCSD
email: agnickolov@mvps.org
MVP VC FAQ: http://www.mvps.org/vcfaq
=====================================

"Vivek" <vivek@nospam.please.com> wrote in message
news:1158201781.566311@goodnews.cos.agilent.com...

Hi,

I would like to know if there is any theoretical size limit for CComBSTR?

It seems like I am coming across some sort of limitation at ~250MB Unicode
string. It may or may not be the user code, however, I would like to know
what the limits are if there are any that does not include the actual
physical memory limitation of the system itself.

For e.g, when I passed on the address of a CComBSTR to a MSXML6 method
that dumps XML content into a CComBSTR, the method came back with the
following error:

"hr = 0x00000003 The system cannot find the path specified."

The limit or what seems to be some sort of a limit seems to be at ~250MB?
Lower sized strings <250MB seem to be fine...