I have run the DebugDiag beta tool and get this result, but was unable
to access the support newsgroup to ask what to do about it. Anyone know
if there has been any hotfixes/patches/known problems with msvbvm50.dll
(on windows 2000)?

Detected possible blocking or leaked critical section at
msvbvm50!Rby_ThreadPool+b4 owned by thread 20 in 3076-1112750616.dmp

Impact of this lock

100.00% of executing ASP Requests blocked

22.86% of threads blocked

(Threads 15 16 17 18 19 21 22 23)

The following functions are trying to enter this critical section

msvbvm50!CMutexSem::Request+10

The following module(s) are involved with this critical section

c:\WINNT\system32\msvbvm50.dll from Microsoft Corporation

Re: IIS debugdiag results - now how to fix it? by Pat

Pat
Thu May 26 23:41:12 CDT 2005

You are running into the VB5 version of the Retain In Memory problem that is
well known for VB6. You have a couple of choices:

1) Re-compile the dll with VB6 and make sure to use the Retain in Memory
flag.
2) Add an empty class to the project, reference it, and re-compile w/VB5


Pat


<bruce.parrott@infinity.co.nz> wrote in message
news:1117165620.106338.63690@z14g2000cwz.googlegroups.com...
>I have run the DebugDiag beta tool and get this result, but was unable
> to access the support newsgroup to ask what to do about it. Anyone know
> if there has been any hotfixes/patches/known problems with msvbvm50.dll
> (on windows 2000)?
>
> Detected possible blocking or leaked critical section at
> msvbvm50!Rby_ThreadPool+b4 owned by thread 20 in 3076-1112750616.dmp
>
> Impact of this lock
>
> 100.00% of executing ASP Requests blocked
>
> 22.86% of threads blocked
>
> (Threads 15 16 17 18 19 21 22 23)
>
> The following functions are trying to enter this critical section
>
> msvbvm50!CMutexSem::Request+10
>
> The following module(s) are involved with this critical section
>
> c:\WINNT\system32\msvbvm50.dll from Microsoft Corporation
>



Re: IIS debugdiag results - now how to fix it? by bruce

bruce
Sun May 29 16:27:46 CDT 2005

But I thought this was a Microsoft dll? I don't have the source code?
Or are you suggesting that something else is calling this dll and
doesn't have the "Retain in Memory" flag set?


Re: IIS debugdiag results - now how to fix it? by Pat

Pat
Mon May 30 00:04:22 CDT 2005

I'm talking about the VB Com object, not the VB Runtime (MSVBVM50.dll).

Pat

<bruce.parrott@infinity.co.nz> wrote in message
news:1117402066.436479.247260@o13g2000cwo.googlegroups.com...
> But I thought this was a Microsoft dll? I don't have the source code?
> Or are you suggesting that something else is calling this dll and
> doesn't have the "Retain in Memory" flag set?
>