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

 ID:                 50737
 Comment by:         pdescham49 at gmail dot com
 Reported by:        jason at lentink dot net
 Summary:            stream_set_blocking creates high cpu usage
 Status:             Bogus
 Type:               Bug
 Package:            Streams related
 Operating System:   Linux
 PHP Version:        5.2.12
 Block user comment: N

 New Comment:

Wow. Nice thread, You'll go far in life with an attitude like that. I
assume you are not being paid for this support. If you were my employee
I would fire you on the spot.


Previous Comments:
------------------------------------------------------------------------
[2010-01-28 08:44:29] [email protected]

Stil a FAIL:



Warning: fsockopen(): php_network_getaddresses: getaddrinfo failed: Name
or service not known 

------------------------------------------------------------------------
[2010-01-15 10:48:09] jason at lentink dot net

Then we go back to the first post and there is a 2 line example of the 

problem.



Reproduce code:

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

<?php

$socket = fsockopen("somehost", 631313, $errno, $errstr);

stream_set_blocking($socket, 0); // non blocking



this is enough to trigger the problem.

I hope this is short enough.

------------------------------------------------------------------------
[2010-01-15 08:56:36] [email protected]

Strike 3. As long as you can not provide a short reproducing script
(like described in my first comment to this report) the bug is most
likely something you did wrong.

------------------------------------------------------------------------
[2010-01-14 12:53:42] jason at lentink dot net

Whatever you want :)



http://www.grasvezel.nl/media/software/cpuload.txt



Here is a complete undressed file which only has the problem.

------------------------------------------------------------------------
[2010-01-14 12:17:19] [email protected]

I asked for small, complete script NOT for a framework.

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


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

    http://bugs.php.net/bug.php?id=50737


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

Reply via email to