From owner-freebsd-hackers Fri Feb 5 12:28:07 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA24961 for freebsd-hackers-outgoing; Fri, 5 Feb 1999 12:28:07 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA24909 for ; Fri, 5 Feb 1999 12:27:59 -0800 (PST) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.9.1/8.9.1) id HAA22959; Sat, 6 Feb 1999 07:04:18 +1100 (EST) (envelope-from jb) From: John Birrell Message-Id: <199902052004.HAA22959@cimlogic.com.au> Subject: Re: Memory leak in pthread? In-Reply-To: from "Sergey S. Kosyakov" at "Feb 5, 1999 5:21:57 pm" To: ks@itp.ac.ru (Sergey S. Kosyakov) Date: Sat, 6 Feb 1999 07:04:18 +1100 (EST) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sergey S. Kosyakov wrote: > This programm very quickly eats all the virtual memory. In "freebsd-hackers > archive" I found some words about thread management by hand. More complicated > program, where stacks are allocated/deallocated by malloc()/free() for each > thread, eats memory not so quickly, but still eats, e.g. resident size (for each You need to detach the threads. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message