Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 33062 invoked from network); 9 Jun 2005 06:01:56 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 9 Jun 2005 06:01:56 -0000 Received: (qmail 50352 invoked by uid 500); 9 Jun 2005 06:01:51 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 50288 invoked by uid 500); 9 Jun 2005 06:01:50 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@cocoon.apache.org List-Id: Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 50273 invoked by uid 99); 9 Jun 2005 06:01:50 -0000 X-ASF-Spam-Status: No, hits=-10.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from minotaur.apache.org (HELO minotaur.apache.org) (209.237.227.194) by apache.org (qpsmtpd/0.28) with SMTP; Wed, 08 Jun 2005 23:01:46 -0700 Received: (qmail 32956 invoked from network); 9 Jun 2005 06:01:35 -0000 Received: from localhost.hyperreal.org (HELO ?127.0.0.1?) (127.0.0.1) by localhost.hyperreal.org with SMTP; 9 Jun 2005 06:01:35 -0000 Message-ID: <42A7DBA2.1@apache.org> Date: Thu, 09 Jun 2005 08:03:14 +0200 From: Carsten Ziegeler User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: dev@cocoon.apache.org Subject: Re: Weird multithreading bug in Cron block References: <42A5D341.5000306@apache.org> <42A76752.3080408@apache.org> In-Reply-To: <42A76752.3080408@apache.org> X-Enigmail-Version: 0.91.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Spam-Rating: localhost.hyperreal.org 1.6.2 0/1000/N X-Virus-Checked: Checked X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Sylvain Wallez wrote: > So the question is: > - why is the pipeline automatically released? Is to avoid memory leaks? > Yes, in 2.1.x there was no good place for explicitly releasing the pipeline; this required some incompatible changes we did in 2.2; the pipelines are released there explicitly and not automatically. If the pipeline is not released properly, this means that all pipeline components are not released, creating a hugh memory leak. Carsten -- Carsten Ziegeler - Open Source Group, S&N AG http://www.s-und-n.de http://www.osoco.org/weblogs/rael/