Bug #15485 Updated: memory ressource with socket_read()

From: Date: Sat, 08 Jun 2002 10:35:36 +0000
Subject: Bug #15485 Updated: memory ressource with socket_read()
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-9832@lists.php.net to get a copy of this message
ID: 15485 Updated by: bool@nexenservices.com Reported By: bool@nexenservices.com -Status: Feedback +Status: Open Bug Type: Sockets related Operating System: Windows 2000 Pro -PHP Version: 4.2.0 +PHP Version: 4.x (latest of 07/06) New Comment: Yes, sorry... I tried. But it doesn't work... It's seem to be exactly like before... Previous Comments: ------------------------------------------------------------------------ [2002-06-08 06:26:45] grangeway2@hotmail.com markus, the comment at 7june,2:32 pm was against the latest snapshot. PHP did not output anything when it terminated. The code in that example was 'broken'. The fixed version of that code was to add a sleep(1). Adding a usleep(100000)(i.e. 1sec), still exhibits the broken behaviour. Adding a sleep(1) command 'fixes' the memory issue. Paul ------------------------------------------------------------------------ [2002-06-08 05:42:41] mfischer@php.net As suggested, please try http://snaps.php.net/win32/php4-win32-latest.zip ------------------------------------------------------------------------ [2002-06-08 05:35:01] bool@boolsite.net I've just test with PHP 4.2.1 (always under Win2k Pro). And there is always the same pb... ------------------------------------------------------------------------ [2002-06-08 05:28:03] mfischer@php.net Please try the latest snapshot at http://snaps.php.net/win32/php4-win32-latest.zip instead, this one contains the current development code. ------------------------------------------------------------------------ [2002-06-08 05:14:32] bool@nexenservices.com It the same things. I try now whith PHP 4.2.1 (sorry, I can't compile with the last version) ------------------------------------------------------------------------ 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/15485 -- Edit this bug report at http://bugs.php.net/?id=15485&edit=1

« previous php.bugs (#9832) next »