Re: more than 100 000 semaphore handles for DLLHOST.exe

From: NO_MSC_NO_MSCP_NO_MSENGINEER (notengo_at_nohay.com)
Date: 12/21/04

  • Next message: NO_MSC_NO_MSCP_NO_MSENGINEER: "Re: more than 100 000 semaphore handles for DLLHOST.exe" 
    Date: Tue, 21 Dec 2004 09:24:08 +0100

    Thanks, I used processxp also from sysinternals

    AND I ALSO HAS HUNDREDS OF SEMAPHORE HANDLES RUNNING OVER THERE...

    "JB" <noone@nowhere.dom> escribió en el mensaje
    news:%23gTezFs5EHA.1260@TK2MSFTNGP12.phx.gbl...
    > Try running "handle.exe" from sysinternals - that will at least show you
    > what type of object the handles represent.
    >
    >
    > NO_MSC_NO_MSCP_NO_MSENGINEER wrote:
    >> Hi, we're running in a very similar problem (see my post here)
    >>
    >> I don't know yet if the handles are semaphor handles, but sometimes they
    >> are so many that they bluescreen our server!!!
    >>
    >> Please, if somebody could help...
    >>
    >>
    >> "S.Cassan" <sylvain.cassan@eads.com> escribió en el mensaje
    >> news:OA2wvRi0EHA.4028@TK2MSFTNGP15.phx.gbl...
    >>
    >>>Hi,
    >>>
    >>>I'm under Windows 2K SP4 and I have a strange behaviour. I call a COM+
    >>>method (Developped in C++) through a proxy. This method call others
    >>>methods
    >>>which are in another COM+ application but in Library mode (Developped in
    >>>VB6
    >>>and C++). The components are not Multithreaded but during the execution
    >>>of
    >>>the method I've seen with perfmon that the process DLLHOST.EXE associated
    >>>with my Server COM+ application used more and more handle of Semaphore
    >>>type
    >>>(and so memory).
    >>>It seems to be the same problem as A Semaphore Leak Was Introduced in
    >>>COM+
    >>>QFE 14 (302845) but I'm in SP4!!
    >>>We have check all the code and we found nothing.
    >>>Any ideas?
    >>>Thanks
    >>>
    >>>Sylvain
    >>>
    >>>
    >>
    >>

  • Next message: NO_MSC_NO_MSCP_NO_MSENGINEER: "Re: more than 100 000 semaphore handles for DLLHOST.exe"
    Loading