Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:43280 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 27123 invoked from network); 9 Mar 2009 10:31:31 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 9 Mar 2009 10:31:31 -0000 Authentication-Results: pb1.pair.com header.from=dmitry@zend.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=dmitry@zend.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain zend.com designates 212.25.124.163 as permitted sender) X-PHP-List-Original-Sender: dmitry@zend.com X-Host-Fingerprint: 212.25.124.163 il-gw1.zend.com Windows 2000 SP4, XP SP1 Received: from [212.25.124.163] ([212.25.124.163:59446] helo=il-gw1.zend.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id EF/82-12606-100F4B94 for ; Mon, 09 Mar 2009 05:31:30 -0500 Received: from ws.home ([10.1.10.37]) by il-gw1.zend.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 9 Mar 2009 12:32:52 +0200 Message-ID: <49B4EFFC.30100@zend.com> Date: Mon, 09 Mar 2009 13:31:24 +0300 User-Agent: Thunderbird 2.0.0.19 (X11/20090105) MIME-Version: 1.0 To: Igor Feghali CC: PHP Developers Mailing List References: <49B0CDD6.5050205@zend.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 09 Mar 2009 10:32:52.0196 (UTC) FILETIME=[6685CA40:01C9A0A2] Subject: Re: [PHP-DEV] Memory Leaks with Objects (no circular reference) From: dmitry@zend.com (Dmitry Stogov) Hi, these caches can't grow over some internal limits and they can't take 128M. It may be some other source of the problem. Could you create a script which reproduces memory overflow? Thanks. Dmitry. Igor Feghali wrote: > Hello Dmitry, > > Thank you for your answer. The problem comes when you put that piece > of code inside a Daemon that is supposed to run 24h/7 days. The > reserved memory increases at each loop, never gets freed, and in about > 1~2 days the process dies because it reaches the memory limit of > 128MB. > > Isn't there any way to force PHP to free that space up ? > > Regards, > ~IF.