Bug #60556 [Com]: php5ts.dll crash when reaching over 1000 requests.

Thu, 08 Nov 2012 00:59:59 -0800 

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

 ID:                 60556
 Comment by:         R at OTMAIL dot COM
 Reported by:        missiontcomputers at hotmail dot com
 Summary:            php5ts.dll crash when reaching over 1000 requests.
 Status:             Feedback
 Type:               Bug
 Package:            Built-in web server
 Operating System:   Windows 7 32bit / SP1
 PHP Version:        5.3.8
 Block user comment: N
 Private report:     N

 New Comment:

تم الاختراق من قبل ملكع هكر ..BY:MLK3 HACKER F-16 
اهنيكم ع حماية ههههههههه 
................ لعيون : ابو شنب هكر . ابو لميس . جمره 
هكر . شيطونه هكر . كوبرا هكر.


Previous Comments:
------------------------------------------------------------------------
[2012-11-08 08:53:56] Q9L_ at HOTMAIL dot COM

تم الاختراق من قبل دكتور سعودي511 Hacked by 
Dr.KsA511تم الاختراق من قبل دكتور سعودي511 Hacked by 
Dr.KsA511تم الاختراق من قبل دكتور سعودي511 Hacked by 
Dr.KsA511تم الاختراق من قبل دكتور سعودي511 Hacked by 
Dr.KsA511تم الاختراق من قبل دكتور سعودي511 Hacked by 
Dr.KsA511تم الاختراق من قبل دكتور سعودي511 Hacked by 
Dr.KsA511تم الاختراق من قبل دكتور سعودي511 Hacked by 
Dr.KsA511تم الاختراق من قبل دكتور سعودي511 Hacked by 
Dr.KsA511تم الاختراق من قبل دكتور سعودي511 Hacked by 
Dr.KsA511تم الاختراق من قبل دكتور سعودي511 Hacked by 
Dr.KsA511تم الاختراق من قبل دكتور سعودي511 Hacked by 
Dr.KsA511تم الاختراق من قبل دكتور سعودي511 Hacked by 
Dr.KsA511تم الاختراق من قبل دكتور سعودي511 Hacked by 
Dr.KsA511تم الاختراق من قبل دكتور سعودي511 Hacked by 
Dr.KsA511تم الاختراق من قبل دكتور سعودي511 Hacked by 
Dr.KsA511تم الاختراق من قبل دكتور سعودي511 Hacked by 
Dr.KsA511تم الاختراق من قبل دكتور سعودي511 Hacked by 
Dr.KsA511تم الاختراق من قبل دكتور سعودي511 Hacked by 
Dr.KsA511تم الاختراق من قبل دكتور سعودي511 Hacked by 
Dr.KsA511تم الاختراق من قبل دكتور سعودي511 Hacked by 
Dr.KsA511تم الاختراق من قبل دكتور سعودي511 Hacked by 
Dr.KsA511تم الاختراق من قبل دكتور سعودي511 Hacked by 
Dr.KsA511تم الاختراق من قبل دكتور سعودي511 Hacked by 
Dr.KsA511تم الاختراق من قبل دكتور سعودي511 Hacked by 
Dr.KsA511تم الاختراق من قبل دكتور سعودي511 Hacked by 
Dr.KsA511تم الاختراق من قبل دكتور سعودي511 Hacked by 
Dr.KsA511

------------------------------------------------------------------------
[2012-08-15 21:05:00] kilbyc at bellsouth dot net

Came up with a simpler test case
Index.php
<?php
exit();
?>

Using the same test parameters in my earlier comment.

------------------------------------------------------------------------
[2012-08-15 20:14:15] kilbyc at bellsouth dot net

This is the simplest test case I could manage. In my production environment, 
the SoapClient doesn't always throw an error.
<?php 
try { 
    $x = new SoapClient("non-existent.wsdl",array("exceptions" => 1)); 
} catch (SoapFault $E) { 
    echo $E->faultstring;
}  
        $doc = new DOMDocument();
    $doc->loadHTML("<html><body>Test<br></body></html>");
    echo $doc->saveHTML();
        //require "require.php";
        gzcompress(serialize(var_export("<html><body>Test<br></body></html>", 
true)),6);
        $restart = time()+5;
?>
As reported, I am using ext that are provided with PHP. php.ini, httpd.conf or 
a zip of the entire problem environment is available upon request.

------------------------------------------------------------------------
[2012-08-15 11:09:55] paj...@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 the script requires a 
database to demonstrate the issue, please make sure it creates 
all necessary tables, stored procedures etc.

Please avoid embedding huge scripts into the report.



------------------------------------------------------------------------
[2012-08-14 17:19:09] kilbyc at bellsouth dot net

It doesnt really bother me that PHP is dying, the thing that is killing me is 
that when one thread dies with 255, Apache picks up and restarts the whole 
child process. I end up with a log file full of thread exited with 255, server 
restarting.

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


The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at

    https://bugs.php.net/bug.php?id=60556


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

Reply via email to