|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #45029 POST requests have an emalloc leak
Submitted: 2008-05-17 17:39 UTC Modified: 2008-05-19 21:57 UTC
From: Assigned:
Status: Not a bug Package: cURL related
PHP Version: 5.3CVS-2008-05-17 (CVS) OS: Linux/FreeBSD
Private report: No CVE-ID: None
View Add Comment Developer Edit
Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know!
Just going to say 'Me too!'? Don't clutter the database with that please !
Your email address:
Solve the problem:
19 + 43 = ?
Subscribe to this entry?

 [2008-05-17 17:39 UTC]
Adding a bug for this so we can track it.

The leak size isn't constant even though the post data size in this example is constant, and the returned data (a dns error, presumably) is the same.  Seems like there is something weird in our postfield handling code in the curl extension.  Note also that it stabilizes somehow, although this is an extremely simplified version of a long-running command-line script that seems to grow on each post with wildly varying post data. 

Reproduce code:
function curl($post) {
  $ch = curl_init();
  curl_setopt($ch, CURLOPT_URL, "www.fdhfkdsslak.bogus");
  curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1);
  if($post) {
    curl_setopt($ch, CURLOPT_POST, 1);
    for($args='',$i=0;$i<75;$i++) $args .= "a=$i&";
    curl_setopt($ch, CURLOPT_POSTFIELDS, $args);
echo "start ".memory_get_usage()."\n";
for($i=0;$i<10;$i++) {
  echo "GET ".memory_get_usage()."\n";
for($i=0;$i<10;$i++) {
  echo "POST ".memory_get_usage()."\n";

Expected result:
No memory_usage increase from one POST request to the next.

Actual result:
start 326616
GET 327256
GET 327276
GET 327276
GET 327276
GET 327276
GET 327276
GET 327276
GET 327276
GET 327276
GET 327276
POST 327516
POST 327588
POST 327652
POST 327712
POST 327892
POST 328064
POST 328228
POST 328384
POST 328528
POST 328628 


Add a Patch

Pull Requests

Add a Pull Request


AllCommentsChangesGit/SVN commitsRelated reports
 [2008-05-19 21:57 UTC]
Never mind.  The combination of an infinitely growing static array and some caching in the memory manager made this look like a PHP bug when it actually wasn't.
PHP Copyright © 2001-2021 The PHP Group
All rights reserved.
Last updated: Mon May 10 05:01:24 2021 UTC