php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #36550 FATAL: emalloc(): Unable to allocate
Submitted: 2006-02-27 21:22 UTC Modified: 2006-03-10 01:00 UTC
Votes:1
Avg. Score:3.0 ± 0.0
Reproduced:1 of 1 (100.0%)
Same Version:0 (0.0%)
Same OS:0 (0.0%)
From: gary dot wilson at coull dot biz Assigned:
Status: No Feedback Package: Unknown/Other Function
PHP Version: 5.1.2 OS: Windows Server 2000
Private report: No CVE-ID: None
Have you experienced this issue?
Rate the importance of this bug to you:

 [2006-02-27 21:22 UTC] gary dot wilson at coull dot biz
Description:
------------
We are running Apache 2.0.55 (with OpenSSL 0.9.8a), Drupal 4.6 with MySQL 5.0.  We run two hardware load balanced servers of identical spec and configuration and are seeing an error on both servers (not at the same times though).

A file that is available within the CMS on network attached storage is downloadable, however on intermittent occasions the client download hangs and well see the following in the Apache error log:

FATAL:  emalloc():  Unable to allocate 2629871 bytes

Apache then restarts.  This is a fairly intermittent problem and is sometimes reproducible on some networks but not consistently reproducible.

Our memory_limit is set to 8M and the downloadable file is 2.6Mb.  I have up-ed this to 32M (as some similar bug reports suggested this).

Research and many articles have pointed to php as the candidate, however knowing where to begin is the problem.  Just a point in the right direction would be extremely helpful.

Regards
Gary


Patches

Add a Patch

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2006-02-28 09:27 UTC] tony2001@php.net
Thank you for this bug report. To properly diagnose the problem, we
need a short but complete example script to be able to reproduce
this bug ourselves. 

A proper reproducing script starts with <?php and ends with ?>,
is max. 10-20 lines long and does not require any external 
resources such as databases, etc.

If possible, make the script source available online and provide
an URL to it here. Try to avoid embedding huge scripts into the report.


 [2006-03-01 16:54 UTC] gary dot wilson at coull dot biz
The memory_limit increase has resulted in the FATAL:  emalloc():  Unable to allocate to not occur again.  However, now we have experienced:
FATAL:  erealloc():  Unable to allocate 1572864 bytes
[Tue Feb 28 14:36:12 2006] [notice] Parent: child process exited with status 1 -- Restarting.

I do not have a sample script as I do not know what it causing this.
 [2006-03-01 19:43 UTC] bjori@php.net
Thank you for this bug report. To properly diagnose the problem, we
need a short but complete example script to be able to reproduce
this bug ourselves. 

A proper reproducing script starts with <?php and ends with ?>,
is max. 10-20 lines long and does not require any external 
resources such as databases, etc.

If possible, make the script source available online and provide
an URL to it here. Try to avoid embedding huge scripts into the report.

Gary: I am sorry, I really am. But without proper reproducable script there is just no way we can even start guessing what is causing this.
 [2006-03-02 11:44 UTC] gary dot wilson at coull dot biz
Thanks for your honesty, if I can identify the code and provide a script, I will submit it soon as :)

Regards
Gary
 [2006-03-10 01:00 UTC] php-bugs at lists dot php dot net
No feedback was provided for this bug for over a week, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".
 
PHP Copyright © 2001-2022 The PHP Group
All rights reserved.
Last updated: Mon Jan 24 20:03:33 2022 UTC