> I have a few customers that receive an ASP500.100 VBScript Compilation
Error
> Out of Memory - after running their servers for several weeks (sometimes
> months).
>
> Before opening a premier case I figure I'll try to get as much debug info
as
> I can. I'm leaning somewhere between Memory Leak (my app) vs. Memory
> Fragmentation. We run Win2k, ASP(VBScript), VB6 COM objects (all are
> unattended execution etc), and the web is running as Medium Pooled, and
most
> are using ADO 2.71.9030+.
>
> The fun part of this is... I haven't been able to reproduce it here in my
> lab.
>
> PerfMon on DLLHOST indicates - Virtual Bytes has been growing towards
1.8gb
> (so I believe I'm hitting 2gb -- although I haven't actually seen it yet),
> and the working set is 850mb-1gb (Session.Current is between 150-300).
> However - even after the machine has gone idle and Sessions.Current drops
to
> 50, the VM size doesn't decrease... although the working set does (down to
> 650mb). These are 24/7 organizations - so there's never a good time to
> attach a debugger.
>
> How do I tell the difference between mem frag and mem leak in a DLLHOSTed
> app ? (umdh returns thousands of suspected leaks - all 0x20 in size...
> nothing Big that I can call the smoking gun)
> What is the overhead of "gflags /i dllhost.exe +ust" ?
> is umdh -snap what I want ?
>
> I've read previous posts regarding things to try... I cannot put my COM
> objects into a COM+ package because we create the ADO.Connection object in
> VBScript and pass it to the different COM objects .... and ADO doesn't
work
> across processes.
>
> Ideas on how to approach this ?
>
> Thanks,
> -Mike
>
>

> I have a few customers that receive an ASP500.100 VBScript Compilation
Error
> Out of Memory - after running their servers for several weeks (sometimes
> months).