Req #66354 [Com]: Allowed memory size in Unknown on line 0

From: Date: Sun, 29 Dec 2013 19:23:50 +0000
Subject: Req #66354 [Com]: Allowed memory size in Unknown on line 0
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-183485@lists.php.net to get a copy of this message
Edit report at https://bugs.php.net/bug.php?id=66354&edit=1

 ID:                 66354
 Comment by:         spam2 at rhsoft dot net
 Reported by:        spam2 at rhsoft dot net
 Summary:            Allowed memory size in Unknown on line 0
 Status:             Not a bug
 Type:               Feature/Change Request
 Package:            Scripting Engine problem
 Operating System:   Linux
 PHP Version:        5.5.7
 Block user comment: N
 Private report:     N

 New Comment:

> The point is that no code is being executed at the time 
> of that error, it would not be useful to tell you the 
> requested path of the request

this is a *wrong* assumption

let the server-admin decide what he thinks is useful for him
hence if i get these messages multiple times for the same of some hundret vhosts it is my job to
investigate if it is a attack from outside or the owner of the vhost triggers these errors and
wonders about a white page while i have to consider if the limits needs to be raised or notify the
customer what he should avoid - to do this i need at minimum the information which of the ten
thousands of scripts on the machine was called


Previous Comments:
------------------------------------------------------------------------
[2013-12-29 19:15:18] krakjoe@php.net

The point is that no code is being executed at the time of that error, it would not be useful to
tell you the requested path of the request, since that would only lead you to think it was something
wrong with a script in particular and it is not, it is down to the initialization of one or several
modules requiring too much memory before script execution can even begin.

------------------------------------------------------------------------
[2013-12-29 12:50:12] spam2 at rhsoft dot net

> There is not always a script being invoked

this is plain wrong, there maybe is no code auf the called script triggered due initialization but
that does not change the fact taht the path of this damned script is for sure known, otherwise the
code without the error could not be executed later

------------------------------------------------------------------------
[2013-12-29 09:05:55] krakjoe@php.net

There is not always a script being invoked; "in unknown" means precisely that there is
_no_ script being invoked, the memory is exhausted by the initialization or some or several modules
in your setup and the engine hasn't even got the stage where it is executing user code, it
would not be useful to report that these kinds of errors happened in any particular code since that
would lead you to look places that can have no impact whatsoever on the error you are experiencing.

There is nothing that we can, or should do about this.

------------------------------------------------------------------------
[2013-12-26 14:18:38] spam2 at rhsoft dot net

Description:
------------
the whole php-error handler needs a rework

it is completly unhelpful get messages with "in unknown"
frankly there is *always* a script invoked and to debug someone needs
to know which script whatever error triggered

on machines with hundrets of vhosts and cronjobs using PHP you have no clue where to look in such
cases and since this error was created on my personal workstation and reported twice in a month i
would like to find what allocates that much memory

such errors are all over the language

[26-Dec-2013 14:47:28 Europe/Vienna] PHP Fatal error:  Allowed memory size of 335544320 bytes
exhausted (tried to allocate 140731389980584 bytes) in Unknown on line 0

Test script:
---------------
by knowing the script there would be nothing to report

Expected result:
----------------
at least the physical path of the running script

Actual result:
--------------
unhelpful error messages


------------------------------------------------------------------------



-- 
Edit this bug report at https://bugs.php.net/bug.php?id=66354&edit=1


Thread (6 messages)

« previous php.bugs (#183485) next »