Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:28911 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 82741 invoked by uid 1010); 17 Apr 2007 21:56:18 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 82725 invoked from network); 17 Apr 2007 21:56:18 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 17 Apr 2007 21:56:18 -0000 Authentication-Results: pb1.pair.com header.from=ceo@l-i-e.com; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=ceo@l-i-e.com; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain l-i-e.com from 67.139.134.202 cause and error) X-PHP-List-Original-Sender: ceo@l-i-e.com X-Host-Fingerprint: 67.139.134.202 o2.hostbaby.com FreeBSD 4.7-5.2 (or MacOS X 10.2-10.3) (2) Received: from [67.139.134.202] ([67.139.134.202:2962] helo=o2.hostbaby.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 5D/50-13518-28245264 for ; Tue, 17 Apr 2007 17:56:18 -0400 Received: (qmail 47322 invoked by uid 98); 17 Apr 2007 21:56:19 -0000 Received: from 127.0.0.1 by o2.hostbaby.com (envelope-from , uid 1013) with qmail-scanner-2.01 (clamdscan: 0.88.7/3109. Clear:RC:1(127.0.0.1):. Processed in 0.087227 secs); 17 Apr 2007 21:56:19 -0000 Received: from localhost (HELO l-i-e.com) (127.0.0.1) by localhost with SMTP; 17 Apr 2007 21:56:19 -0000 Received: from 209.254.223.2 (SquirrelMail authenticated user ceo@l-i-e.com) by www.l-i-e.com with HTTP; Tue, 17 Apr 2007 16:56:19 -0500 (CDT) Message-ID: <3293.209.254.223.2.1176846979.squirrel@www.l-i-e.com> In-Reply-To: <7cea347c0704170116j3ba50dbbrd7cc36780ead7164@mail.gmail.com> References: <7cea347c0704160319x619b26d0s7716e35493e122c4@mail.gmail.com> <4623BDF4.8010005@zend.com> <7cea347c0704170116j3ba50dbbrd7cc36780ead7164@mail.gmail.com> Date: Tue, 17 Apr 2007 16:56:19 -0500 (CDT) To: "David Sklar" Cc: internals@lists.php.net Reply-To: ceo@l-i-e.com User-Agent: Hostbaby Webmail MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Subject: Re: [PHP-DEV] Trapping "memory exhausted" error From: ceo@l-i-e.com ("Richard Lynch") On Tue, April 17, 2007 3:16 am, David Sklar wrote: > Richard Lynch wrote: >> You might also come at it from the other direction and detect/notify >> at some number smaller than the current hard limit, configurable in >> php.ini... >> >> This might play better with anything relying on the current >> behaviour > > This is interesting and might actually take care of a lot of cases. I > don't know enough about the existing memory manager to know if it > would handle the case where a single new allocation would blow through > both the (lower) soft limit and the hard limit at the same time. If an allocation blows through the hard limit, it should behave exactly as it does now, for BC, imho. If you let the developer decide on a "soft limit" or a percentage of the "hard limit" where some callback function happens, it's on their heads if they do something silly that rips right past their selected soft/hard limits. -- Some people have a "gift" link here. Know what I want? I want you to buy a CD from some indie artist. http://cdbaby.com/browse/from/lynch Yeah, I get a buck. So?