From owner-freebsd-threads@FreeBSD.ORG Thu Jul 29 21:30:04 2010 Return-Path: Delivered-To: freebsd-threads@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3DF85106566C for ; Thu, 29 Jul 2010 21:30:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 284C18FC1B for ; Thu, 29 Jul 2010 21:30:04 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o6TLU3VR030073 for ; Thu, 29 Jul 2010 21:30:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o6TLU3Xi030068; Thu, 29 Jul 2010 21:30:03 GMT (envelope-from gnats) Date: Thu, 29 Jul 2010 21:30:03 GMT Message-Id: <201007292130.o6TLU3Xi030068@freefall.freebsd.org> To: freebsd-threads@FreeBSD.org From: Jilles Tjoelker Cc: Subject: Re: threads/148515: Memory / syslog strangeness in FreeBSD 8.x ( possible leak/ threading issue ) X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Jilles Tjoelker List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Jul 2010 21:30:04 -0000 The following reply was made to PR threads/148515; it has been noted by GNATS. From: Jilles Tjoelker To: bug-followup@FreeBSD.org, vikash.badal@is.co.za Cc: Subject: Re: threads/148515: Memory / syslog strangeness in FreeBSD 8.x ( possible leak/ threading issue ) Date: Thu, 29 Jul 2010 23:27:33 +0200 The difference could perhaps be explained by malloc(3) changes. 8.x's malloc tries to keep more memory per-thread, which reduces contention but increases memory usage. By the way, your program may behave erratically when it terminates or when pthread_create() fails because pthread_cancel() may be called on an uninitialized pthread_t, pthread functions are called on detached and terminated threads and the signal handler calls functions that are not async-signal-safe. -- Jilles Tjoelker