From: Giuliano Catrambone <giuliano.catrambone@catrasoftware.it>
To: Stephen Croall <scroall@tibco.com>
Cc: pthreads-win32@sources.redhat.com
Subject: Re: Memory leak with detached threads
Date: Sun, 29 Oct 2006 20:10:00 -0000 [thread overview]
Message-ID: <454518D0.3080106@catrasoftware.it> (raw)
In-Reply-To: <5D819E730A717F47BC9B256CCE55297001C410D6@NA-PA-VBE02.na.tibco.com>
Hi Stephen,
the initial version of the code was using pthread_detach() and I had
the same issue,
a leak about 4KB every 20 iterations.
Do you have some other ideas?
Thanks
giu
Stephen Croall wrote:
> DOH!
>
> Just realised that you are calling pthread_attr_setdetachstate(). You
> could change to calling pthread_detach() to see if the memory leak still
> happens. We use this call a lot in our code and have no problems with
> leaks.
>
> Steve.
>
>
>
--
-----------------------------------------------------------------
Giuliano Catrambone
Director, Professional Services
Open source projects:
http://sourceforge.net/projects/catralibraries/
http://sourceforge.net/projects/openstreaming/
CatraSoftware:
Home page: http://www.catrasoftware.it
Streaming page:
http://www.catrasoftware.it/Streaming/CatraStreamingPlatform.htm
Mobile +39.393.8816655
Fixed: +39.02.90377228
Skype: Catrambone Giuliano
msn: giulianocatrambone@hotmail.com
Jabber: giuliano.catrambone@Jabber.org
Yahoo: giuliano.catrambone
-----------------------------------------------------------------
next prev parent reply other threads:[~2006-10-29 20:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-29 19:02 Stephen Croall
2006-10-29 20:10 ` Giuliano Catrambone [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-10-29 18:54 Stephen Croall
2006-10-29 18:42 Giuliano Catrambone
2006-10-29 20:20 ` Tim Theisen
2006-10-30 22:03 ` Giuliano Catrambone
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=454518D0.3080106@catrasoftware.it \
--to=giuliano.catrambone@catrasoftware.it \
--cc=pthreads-win32@sources.redhat.com \
--cc=scroall@tibco.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).