Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:94014 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 51024 invoked from network); 15 Jun 2016 15:34:43 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 15 Jun 2016 15:34:43 -0000 Authentication-Results: pb1.pair.com smtp.mail=mamfelt@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=mamfelt@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.217.169 as permitted sender) X-PHP-List-Original-Sender: mamfelt@gmail.com X-Host-Fingerprint: 209.85.217.169 mail-lb0-f169.google.com Received: from [209.85.217.169] ([209.85.217.169:33655] helo=mail-lb0-f169.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id F7/71-41914-29571675 for ; Wed, 15 Jun 2016 11:34:43 -0400 Received: by mail-lb0-f169.google.com with SMTP id xp5so3846114lbb.0 for ; Wed, 15 Jun 2016 08:34:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=F1jwv8PEnp7oKh+659dviIPtIjyyqFrBr5wo6qLasBg=; b=Rn5vZL6gk/E6+r+aRAQ8gCGdolEeRONA8dDlQde+veY6jGW/j8hQhf2zBsnj8P6hdd PG2rP6DKVXNej+6uArJIoRXZElUhHSNlFTYXnXoCwm4yPIg1l6y9WkHfiSWiOpvoe92v HXUtqNWgmnhGcEIs24dhKvYdMUUgLttG36s5LNrPH8ob+Sx1JEhXbE/t151KrXlgiT6D WGvZhvk9B5AiSTBwywh0AsXqSm/FdARGFfNm9cVvF0A0TvjwMxjqfeAzDnCT5uQNHeb9 SeAfJYPQksuKN0nOSC6tmBvy1UpYGkyobHLPCV9r0NdeIG1gmtHyUAfLSk7pNMjHR4pg FkkA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=F1jwv8PEnp7oKh+659dviIPtIjyyqFrBr5wo6qLasBg=; b=CtwIkQObi0iSTRquRpENnLGiPJERwRcThXZS5se/sUIUdpRkd0KL3IRL2gf03FUUJQ 1NVT4I4XsVcj2wJKmPL6Ves2Qn1V7BjpHCpEqt8hAElOG81KEK96IkwIGCARzCfMHk7z 6/MEuG6UAj8uA4zYHFTlTaqrUG+Mh8Bb4SDl9d3QAV7ZxvseOjoF/Sz5nkgAwKLJYnMV QseyzozVxPb0tdLEmwYuSG7m2eQh1jZeG83VRyGuAhurFVBC/A30HUz/M9EHQCA/qETw VhX2G+jkQ4INEdJVojrqB9vwtZVh+4AQ5dM5w2cFAk+ChUEvB5L27FDa7uSKZZ3QHzVs wcHg== X-Gm-Message-State: ALyK8tLioxLXv05WiGcusjrXQiGqobOqEUpm6dV3XhVunSA1+Q8ifFuHFBhdFKJ3fyPUFw== X-Received: by 10.28.178.135 with SMTP id b129mr10408830wmf.60.1466004878691; Wed, 15 Jun 2016 08:34:38 -0700 (PDT) Received: from [10.119.147.187] ([213.27.137.242]) by smtp.gmail.com with ESMTPSA id r129sm10266885wmr.20.2016.06.15.08.34.37 for (version=TLSv1/SSLv3 cipher=OTHER); Wed, 15 Jun 2016 08:34:38 -0700 (PDT) To: internals@lists.php.net References: <4771c925-65e1-536f-e573-250dc99f2e39@gmail.com> Message-ID: <0e11e396-48be-ae7d-4a7a-8b964d2cf128@gmail.com> Date: Wed, 15 Jun 2016 17:34:39 +0200 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.1 MIME-Version: 1.0 In-Reply-To: <4771c925-65e1-536f-e573-250dc99f2e39@gmail.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] PHP allocating too much memory From: mamfelt@gmail.com (Michael Felt) On 15-Jun-16 15:55, Rowan Collins wrote: > On 15/06/2016 14:01, Peter LeBrun wrote: >> The weirdest part about this is that PHP is somehow trying to allocate >> 140TB of memory. > > I've seen numbers like that a few times - always around 140TB, but the > exact number varies. I assume it's an overflow (or underflow?) > somewhere, but the exact mechanism escapes me. (It's close to 2^47, > but not very close; I've got examples logged as "low" as > 140090229815192, and I think I've seen under 140 trillion.) In hex: 00007F694C627798 - so apparently 00007F69400000000 is common to all. FYI: I have seen similar issues with mixed environments (32 and 64-bit) - at this point I am surprised that you can even dlopen() both sizes (my OS now refuses to dlopen() 32-bit modules aka shared libraries when 64-bit application and v.v.) > Apart from sheer curiosity of where this magic number comes from, I > wonder if there is some sanity check missing in the memory manager to > at least display a different error message... > > Regards,