Re: # of current physical Threads > 4 000 000 0000

It seems that it decremented from 0, giving you 0xFFFFFFFF
(4294967295). If it's less than this then the counter got incremented
after the incorrect decrement of 1 from 0.

Shawn B. wrote:
usually, performance counters are used with Increment() and Decrement()
call, not by setting the counter to its actual value.

So I guess, there were three more decrements than increments here...


If that's the case, then there's a thread/memory leak. With that many
threads/locks, I suspect the machine is very slow and non - responsive. If
it is fast and very responsive, then the number simply means that the
decrement wasn't called the same number of times as increment or that it is
the wrong performance counter.


Thanks,
Shawn

.

Relevant Pages

  • Re: IPC resource access counting problem
    ... InterlockedIncrement to increment the value, not ++!), program B opens and ... remove its process ID and decrement count ... construction decrements the counter, each destruction increments it. ... BTW DeleteFile is documented as dodgy: ...
    (microsoft.public.vc.mfc)
  • Re: IPC resource access counting problem
    ... InterlockedIncrement to increment the value, not ++!), program B opens and ... remove its process ID and decrement count ... construction decrements the counter, each destruction increments it. ... BTW DeleteFile is documented as dodgy: ...
    (microsoft.public.vc.mfc)
Loading