Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:15420 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 81405 invoked by uid 1010); 13 Mar 2005 22:00:45 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 81390 invoked from network); 13 Mar 2005 22:00:45 -0000 Received: from unknown (HELO php.net) (127.0.0.1) by localhost with SMTP; 13 Mar 2005 22:00:45 -0000 X-Host-Fingerprint: 212.204.192.51 jdi.jdimedia.nl Linux 2.5 (sometimes 2.4) (4) Received: from ([212.204.192.51:38984] helo=jdi.jdimedia.nl) by pb1.pair.com (ecelerity HEAD r(5124)) with SMTP id 95/FF-31540-C08B4324 for ; Sun, 13 Mar 2005 17:00:45 -0500 Received: from localhost (localhost [127.0.0.1]) by jdi.jdimedia.nl (8.12.11/8.12.11) with ESMTP id j2DM0gO2002306 for ; Sun, 13 Mar 2005 23:00:42 +0100 Received: from jdi.jdimedia.nl ([127.0.0.1]) by localhost (jdi.jdimedia.nl [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 31723-05-2 for ; Sun, 13 Mar 2005 23:00:42 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by jdi.jdimedia.nl (8.12.11/8.12.11) with ESMTP id j2DM0Z4K002288; Sun, 13 Mar 2005 23:00:36 +0100 Date: Sun, 13 Mar 2005 23:00:37 +0100 (CET) X-X-Sender: derick@localhost To: Wez Furlong cc: PHP Development In-Reply-To: <4e89b42605031206177b564e50@mail.gmail.com> Message-ID: References: <4e89b42605031206177b564e50@mail.gmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by amavisd-new at jdimedia.nl Subject: Re: [PHP-DEV] Weird time-sensitive leaks / problems in the memory manager From: derick@php.net (Derick Rethans) On Sat, 12 Mar 2005, Wez Furlong wrote: > Yesterday I saw some leaks with foreach() and custom zend_iterators. > Today, the same binary doesn't have those leaks. > > I had another similar issue a few weeks back on a different machine, > but with an overrun reported on shutdown. The next day, the same > binary was fine. > > Unless the linux-fairy visited both those boxes overnight and > magically fixed the bugs, I think we have an issue either in the > memory manager, or worse, in some other piece of code that is subtly > mangling the memory manager headers. (this is with HEAD). > > Valgrind shows no problems. Even with the zend memory manager disabled? I suspect it will show uninitialized data when you try that... Derick -- Derick Rethans http://derickrethans.nl | http://ez.no | http://xdebug.org