From: Lavanya Swetharanyan <lavanya@psatellite.com>
To: Jef Gearhart <jef@tpssys.com>
Cc: pthreads-win32@sources.redhat.com
Subject: Re: Unix vs. Windows Posix threads !
Date: Wed, 07 Jul 2004 18:09:00 -0000 [thread overview]
Message-ID: <D4C05826-D040-11D8-BE46-000393C91F86@psatellite.com> (raw)
In-Reply-To: <40EC389F.8060302@tps.com>
Thanks. I ran the application and opened the task manager as suggested.
The thread count is constant at 6. The handle though are increasing
continuously. Even when the delta memory is 0 the handle count is
increasing. The delta mem varies from 0-4-8 K every time the screen
refreshes on its own. What does this increasing number of handles mean
?. Is it causing the memory leak ?. I am also using windows sockets
apart from pthreads.
next prev parent reply other threads:[~2004-07-07 18:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-07 17:46 Lavanya Swetharanyan
2004-07-07 17:54 ` Jef Gearhart
2004-07-07 18:09 ` Lavanya Swetharanyan [this message]
2004-07-07 19:31 ` Jef Gearhart
2004-07-07 20:34 Kok YihTzye-CYK011
2004-07-07 20:56 ` Lavanya Swetharanyan
2004-07-07 23:35 5qduh001
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=D4C05826-D040-11D8-BE46-000393C91F86@psatellite.com \
--to=lavanya@psatellite.com \
--cc=jef@tpssys.com \
--cc=pthreads-win32@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).