You only have (generally speaking) a 2GB address space. Are you running out
of heap? One issue with the LOH is that free space is not compacted, so if
you're allocating huge gobs of memory and fragment the LOH, you can wind up
with a allocation request that can't be fulfilled. Also, the LOH heap does
not include any interop bytes. Also, my experiments on some perf issues that
I've worked on seems to indicate that the reported size of the LOH is the
maximum watermark, rather than a current snapshot (perhaps due to the LOH
not being compacted).
What do the other perf counters tell you? .NET CLR Memory/ # Bytes in all
heaps, tells you your current heap status in all generations including the
LOH.
Check the Process/Private Bytes perf counter, which is a counter that looks
at your process, rather than the .NET runtime only.
Another thing I've done is to use WinDBG and the SOS extension - you can get
a great deal of information about memory issues. You can also use SOS inside
Visual Studio, but I haven't encountered any nasty perf issues since I heard
that bit of news, so I have no real info there.

Signature
Mickey Williams
Author, "Visual C# .NET Core Ref", MS Press
www.neudesic.com
www.servergeek.com
> Hi,
>
[quoted text clipped - 30 lines]
>
> Alex
Alex - 14 Oct 2004 13:19 GMT
Thanks Williams
I have dumped my application's managed heap using WinDBG(scenario:with 10
numbers of 16MB LongRaw data). There is no big object is rooted to get
leaked.
Then I profiled the application with Performance Monitor for OutOfMemory
scenario.For #Bytes in All Heaps,the graph is going up and down regulary,but
Private Bytes keep growing and eventually I am getting the OutOfMemory
exception.Pretends memory leak happens in the native memory.
Is there any memory leak issue in OleDb provider, for Blob operations?
To avoid OleDb,tried with MS Oracle Provider.For big blobs I am getting
ORA-01406:fetched column value was truncated exception.
And Oracle Data Provider does not support more than 32512 bytes.
Currently I have no other option other than OleDb to access the Long Raw
data.Please send the comments.
Thanks
Alex
> You only have (generally speaking) a 2GB address space. Are you running out
> of heap? One issue with the LOH is that free space is not compacted, so if
[quoted text clipped - 50 lines]
> >
> > Alex