RE: Looks like Cygwin don't close sometimes event descriptors

RE: Looks like Cygwin don't close sometimes event descriptors

[Ivan Begtin]

Hi again, thanks for fast reply.

I use W2K Prof and still haven't tried this scenario with 1.3.3. 
As I remember I had same problem with v1.1.7 then I ported multithreaded
program to Cygwin. 
Process Explorer (HandleEx in past) don't show their names, just number.
Console utility handle show them but also without names.


Ivan

-----Original Message-----
From: egor duda [ mailto:deo@logos-m.ru ]
Sent: Friday, September 21, 2001 4:11 PM
To: Ivan Begtin
Cc: cygwin@cygwin.com
Subject: Re: Looks like Cygwin don't close sometimes event descriptors


Hi!

Friday, 21 September, 2001 Ivan Begtin ibegtin@biolink.com.ru wrote:

IB>   I am using cygwin v1.3.2 for now and I've tried to compile
net-snmp
IB> v4.2.1with cygwin.

have you tried this scenario with 1.3.3? what OS are you using?

IB> Started snmpd.exe.
IB>   When I launched "snmpwalk localhost public" number of descriptors
used
IB> by snmpd.exe immediately growed
IB>   So after starting "snmpwalk localhost public" in simple cycle.
Number
IB> of descriptors reached 12000 (or more) and they all were open long
time
IB> (until i stopped snmpd.exe).
IB>   Launching handle.exe form http://www.sysinternals.com shows that
most
IB> of open descriptors are Events. 
IB>   Well, I just want to know is it bug or it's normal and shouldn't
be a
IB> problem? 

and by launching HandleEx from sysinternals you've found that their
names are ...?

it's clearly a bug, though it's not clear yet whether it's cygwin of
snmpd bug.

Egor.            mailto:deo@logos-m.ru ICQ 5165414 FidoNet 2:5020/496.19



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Looks like Cygwin don't close sometimes event descriptors

[Corinna Vinschen]

On Fri, Sep 21, 2001 at 04:33:22PM +0400, Ivan Begtin wrote:
> Hi again, thanks for fast reply.
> 
> I use W2K Prof and still haven't tried this scenario with 1.3.3. 
> As I remember I had same problem with v1.1.7 then I ported multithreaded
> program to Cygwin. 
> Process Explorer (HandleEx in past) don't show their names, just number.
> Console utility handle show them but also without names.

Coud you try using WinObj from sysinternals?  It shows all
objects in the NT internal namespace.  The events (all beginning
with "cyg") should be in the subfolder "BaseNamedObjects".

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin@cygwin.com
Red Hat, Inc.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Looks like Cygwin don't close sometimes event descriptors

[egor duda]

Hi!

Friday, 21 September, 2001 Ivan Begtin ibegtin@biolink.com.ru wrote:

please, keep your answers to the list. i'm intentionally setting
Reply-To: address to point to the list because i don't want to receive
2 copies of each message.

IB> I use W2K Prof and still haven't tried this scenario with 1.3.3.

then i think you should try to. 1.3.3 contains a lot of fixes/changes

IB> As I remember I had same problem with v1.1.7 then I ported multithreaded
IB> program to Cygwin. 
IB> Process Explorer (HandleEx in past) don't show their names, just number.
IB> Console utility handle show them but also without names.

do you mean it doesn't show names of all events or only those that are
leaking? HandleEx does show the names for named events, so we have 2
possibilities here -- either these are anonymous events (which may
help to track them down) or Process Explorer is missing needed
functionality in which case you should try to use original HandleEx.

IB> -----Original Message-----
IB> From: egor duda [ mailto:deo@logos-m.ru ]
IB> Sent: Friday, September 21, 2001 4:11 PM
IB> To: Ivan Begtin
IB> Cc: cygwin@cygwin.com
IB> Subject: Re: Looks like Cygwin don't close sometimes event descriptors

IB> Hi!

IB> Friday, 21 September, 2001 Ivan Begtin ibegtin@biolink.com.ru wrote:

IB>>   I am using cygwin v1.3.2 for now and I've tried to compile
IB> net-snmp
IB>> v4.2.1with cygwin.

IB> have you tried this scenario with 1.3.3? what OS are you using?

IB>> Started snmpd.exe.
IB>>   When I launched "snmpwalk localhost public" number of descriptors
IB> used
IB>> by snmpd.exe immediately growed
IB>>   So after starting "snmpwalk localhost public" in simple cycle.
IB> Number
IB>> of descriptors reached 12000 (or more) and they all were open long
IB> time
IB>> (until i stopped snmpd.exe).
IB>>   Launching handle.exe form http://www.sysinternals.com shows that
IB> most
IB>> of open descriptors are Events. 
IB>>   Well, I just want to know is it bug or it's normal and shouldn't
IB> be a
IB>> problem? 

IB> and by launching HandleEx from sysinternals you've found that their
IB> names are ...?

IB> it's clearly a bug, though it's not clear yet whether it's cygwin of
IB> snmpd bug.

Egor.            mailto:deo@logos-m.ru ICQ 5165414 FidoNet 2:5020/496.19


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Looks like Cygwin don't close sometimes event descriptors

[Robert Collins]

----- Original Message -----
From: "Corinna Vinschen" <cygwin@cygwin.com>
To: <cygwin@cygwin.com>
Sent: Friday, September 21, 2001 10:44 PM
Subject: Re: Looks like Cygwin don't close sometimes event descriptors


> On Fri, Sep 21, 2001 at 04:33:22PM +0400, Ivan Begtin wrote:
> > Hi again, thanks for fast reply.
> >
> > I use W2K Prof and still haven't tried this scenario with 1.3.3.
> > As I remember I had same problem with v1.1.7 then I ported
multithreaded
> > program to Cygwin.
> > Process Explorer (HandleEx in past) don't show their names, just
number.
> > Console utility handle show them but also without names.
>
> Coud you try using WinObj from sysinternals?  It shows all
> objects in the NT internal namespace.  The events (all beginning
> with "cyg") should be in the subfolder "BaseNamedObjects".
>

Process Explorer normally does show names - these could be anonymous
objects. Still worth checking though.

Rob


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

RE: Looks like Cygwin don't close sometimes event descriptors

[Ivan Begtin]

Hi!
  Well, Process Explorer don't show these leaking events at all, only
command-line
utility handle.exe from SysInternals shows them (don't know why).
Ok. I will try Cygwin 1.3.3 as soon as possible.

Ivan

-----Original Message-----
From: egor duda [ mailto:deo@logos-m.ru ]
Sent: Friday, September 21, 2001 5:27 PM
To: Ivan Begtin
Cc: cygwin@cygwin.com
Subject: Re: Looks like Cygwin don't close sometimes event descriptors


Hi!

Friday, 21 September, 2001 Ivan Begtin ibegtin@biolink.com.ru wrote:

please, keep your answers to the list. i'm intentionally setting
Reply-To: address to point to the list because i don't want to receive
2 copies of each message.

IB> I use W2K Prof and still haven't tried this scenario with 1.3.3.

then i think you should try to. 1.3.3 contains a lot of fixes/changes

IB> As I remember I had same problem with v1.1.7 then I ported
multithreaded
IB> program to Cygwin. 
IB> Process Explorer (HandleEx in past) don't show their names, just
number.
IB> Console utility handle show them but also without names.

do you mean it doesn't show names of all events or only those that are
leaking? HandleEx does show the names for named events, so we have 2
possibilities here -- either these are anonymous events (which may
help to track them down) or Process Explorer is missing needed
functionality in which case you should try to use original HandleEx.

IB> -----Original Message-----
IB> From: egor duda [ mailto:deo@logos-m.ru ]
IB> Sent: Friday, September 21, 2001 4:11 PM
IB> To: Ivan Begtin
IB> Cc: cygwin@cygwin.com
IB> Subject: Re: Looks like Cygwin don't close sometimes event
descriptors

IB> Hi!

IB> Friday, 21 September, 2001 Ivan Begtin ibegtin@biolink.com.ru wrote:

IB>>   I am using cygwin v1.3.2 for now and I've tried to compile
IB> net-snmp
IB>> v4.2.1with cygwin.

IB> have you tried this scenario with 1.3.3? what OS are you using?

IB>> Started snmpd.exe.
IB>>   When I launched "snmpwalk localhost public" number of descriptors
IB> used
IB>> by snmpd.exe immediately growed
IB>>   So after starting "snmpwalk localhost public" in simple cycle.
IB> Number
IB>> of descriptors reached 12000 (or more) and they all were open long
IB> time
IB>> (until i stopped snmpd.exe).
IB>>   Launching handle.exe form http://www.sysinternals.com shows that
IB> most
IB>> of open descriptors are Events. 
IB>>   Well, I just want to know is it bug or it's normal and shouldn't
IB> be a
IB>> problem? 

IB> and by launching HandleEx from sysinternals you've found that their
IB> names are ...?

IB> it's clearly a bug, though it's not clear yet whether it's cygwin of
IB> snmpd bug.

Egor.            mailto:deo@logos-m.ru ICQ 5165414 FidoNet 2:5020/496.19



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Looks like Cygwin don't close sometimes event descriptors

[egor duda]

Hi!

Friday, 21 September, 2001 Ivan Begtin ibegtin@biolink.com.ru wrote:

IB>   I am using cygwin v1.3.2 for now and I've tried to compile net-snmp
IB> v4.2.1with cygwin.

have you tried this scenario with 1.3.3? what OS are you using?

IB> Started snmpd.exe.
IB>   When I launched "snmpwalk localhost public" number of descriptors used
IB> by snmpd.exe immediately growed
IB>   So after starting "snmpwalk localhost public" in simple cycle. Number
IB> of descriptors reached 12000 (or more) and they all were open long time
IB> (until i stopped snmpd.exe).
IB>   Launching handle.exe form http://www.sysinternals.com shows that most
IB> of open descriptors are Events. 
IB>   Well, I just want to know is it bug or it's normal and shouldn't be a
IB> problem? 

and by launching HandleEx from sysinternals you've found that their
names are ...?

it's clearly a bug, though it's not clear yet whether it's cygwin of
snmpd bug.

Egor.            mailto:deo@logos-m.ru ICQ 5165414 FidoNet 2:5020/496.19


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Looks like Cygwin don't close sometimes event descriptors

[Ivan Begtin]

Hi all.
  I am using cygwin v1.3.2 for now and I've tried to compile net-snmp
v4.2.1with cygwin. Started snmpd.exe.
  When I launched "snmpwalk localhost public" number of descriptors used
by snmpd.exe immediately growed
  So after starting "snmpwalk localhost public" in simple cycle. Number
of descriptors reached 12000 (or more) and they all were open long time
(until i stopped snmpd.exe).
  Launching handle.exe form http://www.sysinternals.com shows that most
of open descriptors are Events. 
  Well, I just want to know is it bug or it's normal and shouldn't be a
problem? 

Best regards, 
  Ivan Begtin



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/