Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:57454 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 69217 invoked from network); 20 Jan 2012 07:10:05 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 20 Jan 2012 07:10:05 -0000 Authentication-Results: pb1.pair.com smtp.mail=smalyshev@sugarcrm.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=smalyshev@sugarcrm.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 207.97.245.133 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 207.97.245.133 smtp133.iad.emailsrvr.com Linux 2.6 Received: from [207.97.245.133] ([207.97.245.133:46745] helo=smtp133.iad.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 73/84-42843-C43191F4 for ; Fri, 20 Jan 2012 02:10:04 -0500 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp43.relay.iad1a.emailsrvr.com (SMTP Server) with ESMTP id 1E0F72D01BD; Fri, 20 Jan 2012 02:10:02 -0500 (EST) X-Virus-Scanned: OK Received: by smtp43.relay.iad1a.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id 679B32D010D; Fri, 20 Jan 2012 02:10:01 -0500 (EST) Message-ID: <4F191348.5060102@sugarcrm.com> Date: Thu, 19 Jan 2012 23:10:00 -0800 Organization: SugarCRM User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:9.0) Gecko/20111222 Thunderbird/9.0.1 MIME-Version: 1.0 To: Pierrick Charron CC: Stanislav Malyshev , David Soria Parra , Internals References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Remove memory leak in PHP5.4 for bug 55971 From: smalyshev@sugarcrm.com (Stas Malyshev) Hi! > I did run the test of bug #55871 and got memory leaks. This patch > remove them. Could you please review the patch and if it is Ok i'll > commit it to 5.4 Please hold it for now. It's not a critical issue, if we'd have another RC for different reason, we can also have it in as it doesn't look to dangerous. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227