"SCM_Dude" wrote:

> 1) Unfortunately, we are not aware of any way, how to reproduce this issue.
> It seems it raises in a randomly fashion, without any dependencies to time or
> site server conditions.
>
> 2) Here's the call stack of one case. From the listing we see the offending
> routine is deep in framework code library (mscorwks.dll), without any Radiant
> interference.
>
> Thread 12384 stack frames:
> ==========================
> 9 0x090DF984 0x79238072 mscorwks.dll:DllGetClassObjectInternal + 0x131F
> 8 0x090DF9B0 0x792389AF mscorwks.dll:DllGetClassObjectInternal + 0x1C5C
> 7 0x090DFA0C 0x7923851B mscorwks.dll:DllGetClassObjectInternal + 0x17C8
> 6 0x090DFA4C 0x79238D55 mscorwks.dll:DllGetClassObjectInternal + 0x2002
> 5 0x090DFA6C 0x7923A404 mscorwks.dll:DllGetClassObjectInternal + 0x36B1
> 4 0x090DFA9C 0x792CE558 mscorwks.dll:ReleaseFusionInterfaces + 0x28E98
> 3 0x090DFAB8 0x791B3C64 mscorwks.dll:#80 - 0x2307CC
> 2 0x090DFAC8 0x791DBE2F mscorwks.dll:GetCompileInfo + 0xE7E
> 1 0x090DFAE8 0x791DC002 mscorwks.dll:GetCompileInfo + 0x1051
> 0 0x090DFB68 0x0829226B
>
> "Gaurav Khanna [MSFT]" wrote:
>
> > Hi John,
> >
> > Do you have (or, can create) a repro for this issue? What's the callstack
> > when you notice that code in mscorwks.dll is executing?
> >
> > Thanks!
> > Gaurav Khanna
> > http://www.wintoolzone.com/
> > http://www.wintoolzone.com/blog/
> >
> > This posting is provided "AS IS" with no warranties, and confers no rights.
> >
> > > it seems we have encountered a problem in the Microsoft .NET Common
> > > Language Runtime library for Windows Workstation, i.e. "mscorwks.dll".
> > > Our software runs on servers using the library version 1.1.4322.573
> > > (MS .NET 1.1 Service Pack 1 not installed), however we have verified
> > > the SP1 (version 1.1.4322.2032) also does not fix this issue.
> > >
> > > The technical description of the problem follows:
> > >
> > > From time to time, our batch hand held service consumes all available
> > > CPU cycles. We were not able to reproduce this problem in our lab,
> > > however we have about 350 installations in the field and these cases
> > > appear for about 5x in a week. We were able to pin-point the very tiny
> > > loop, in which the affected thread spins. Although we can not exclude
> > > the thread is led into this situation by our code, from the thread's
> > > stack trace we see it is executing only Microsoft's code stored in the
> > > "mscorwks.dll" library.
> > >
> > > Has anyone else experieneced a similar issue?
> > >
> >
> >