Re: Newbie: CComBSTR limitation?

Tech-Archive recommends: Fix windows errors by optimizing your registry

Hi Alexander,


Thanks for prompt response. Moving to x64 is currently not an option and I have the /3GB Windows O/S switch enabled on my XP machine that has 4GB of physical memory.

However, the interesting aspect about this particular incident is that I got the error message when the application utilized only ~690MB of memory and there was plenty left for allocation...

So I take it from your response that there is no limit on how large a CComBSTR/BSTR can be?

I still don't get how I got the following error message from that method in VC++ 2005 debugger:

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


Regards,

Vivek


Alexander Nickolov wrote:
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.

.

Relevant Pages

  • Re: Moving memory blocks in Forth
    ... made some tests on the speed of a routine for moving a block of N words ... Moving memory blocks requires two memory pointers and as high level ... Forth has only the top of stack as a pointer a high level version ... If you are designing the processor then you can select ...
    (comp.lang.forth)
  • Re: Borland Delphi + 64Bits
    ... Moving less is almost always faster than moving more. ... Crossing cache lines creates memory fetch ... Sign extending a value in a register is trivial because it's in the ... extension - 1 clock. ...
    (borland.public.delphi.non-technical)
  • Re: Understanding I/O behaviour - next try
    ... The basic setup is a dual x86_64 box with 8 GB of memory. ... cache. ... The problematic behaviour comes when we are moving large files ...
    (Linux-Kernel)
  • Re: Mixed mode __pin internals: does __pin does anything at all?
    ... the GC to prevent moving the buffer in memory (and not manipulate any ... Is it possible to prevent the GC from moving memory in the first ... a collection of buffers to be used by the App, ... >> Why there is no GC manipulation code? ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Limit on number of Modules/forms?
    ... Thank you all for your prompt response. ... need to be re-designed since it started to grow with no concrete direction. ... memory error and it does not allow me to add more files to the project. ... I tried merging a couple of modules and that let me to add now another ...
    (microsoft.public.vb.general.discussion)