#50312 [Opn]: Opening an https using fopen consumes all cpu time

ID: 50312 Updated by: pajoye@php.net Reported By: kvr at centrum dot cz Status: Open Bug Type: HTTP related Operating System: Linux, Debian PHP Version: 5.3SVN-2009-11-27 (snap) New Comment: IIRC I did not blew it, I was simply not able to reproduce this problem, same as here. I did not blindly apply the patch as every attempt to fix smtg that was not reproducable always had bad side effect. I'm still not able to reproduce, Rasmus, feel free to take the hand on both bugs if you can reproduce these problems and can fix them. Previous Comments: ------------------------------------------------------------------------ [2009-11-27 18:37:23] kvr at centrum dot cz Yes, it looks related. The patch looks quite logical but I'm not sure if it would work with stream_select() functions. Anyway, thank you and sorry the bug report was not clear from the first description. ------------------------------------------------------------------------ [2009-11-27 18:24:29] rasmus@php.net This was reported before and a patch supplied but Pierre blew it off. See bug #46685 The patch there looks sane. I'll try to get some time this weekend to play with it. ------------------------------------------------------------------------ [2009-11-27 18:14:41] kvr at centrum dot cz php (or OpenSSL library) doesn't handle the error code EAGAIN and instead of waiting for data using select() or poll(), it calls read() again and again, taking all the cpu time. ------------------------------------------------------------------------ [2009-11-27 18:04:20] jani@php.net Yes, it's the OpenSSL lib doing the read, what's the bug here? ------------------------------------------------------------------------ [2009-11-27 17:56:41] kvr at centrum dot cz Yes, I tried it exactly as written in your example. The php version was the latest: ~/iphp/bin/php -v PHP 5.3.2-dev (cli) (built: Nov 27 2009 17:39:57) Copyright (c) 1997-2009 The PHP Group Zend Engine v2.3.0, Copyright (c) 1998-2009 Zend Technologies Did you check the strace output (or whatever tool your system provides to trace program syscalls) ? Could you please attach it? ------------------------------------------------------------------------ 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/50312 -- Edit this bug report at http://bugs.php.net/?id=50312&edit=1