Bug #10775 Updated: Apache process in loop after allocation of first session

From: Date: Fri, 15 Jun 2001 03:39:05 +0000
Subject: Bug #10775 Updated: Apache process in loop after allocation of first session
Groups: php.dev 
Request: Send a blank email to php-dev+get-56968@lists.php.net to get a copy of this message
ID: 10775 Updated by: sniper Reported By: peter@helpnet.com.au Old-Status: Open Status: Closed Bug Type: *Session related Operating system: PHP Version: 4.0.5 Assigned To: Comments: This should be fixed in latest CVS. Try snapshot from http://www.zend.com/snapshots/ Previous Comments: --------------------------------------------------------------------------- [2001-05-10 01:21:20] peter@helpnet.com.au Using Apache 1.3.19, PHP 4.0.5, MySQL from April download. The web site has worked with several releases of Apache, PHP and MySQL (except an early PHP release 4 XML). I added MySQL based session code from another site working happily with older versions of everything. When I start a page that has session code, the session open, read, write and close functions complete, the page displays ok but Apache is left in a loop using 100% CPU. I cannot get in to subsequent pages to test anything until I shut down Apache. After I restart Apache, I can see the session record in MySQL and a log in a disk file complete with entries from open, read, write and close. I made the minimum changes to the 4.0.5 php.ini, turned off all magic quotes, added PostgreSQL, but nothing related to sessions and nothing over the last few weeks. The error seems to happen after the last of my code has finished so the session stuff is setting up something to explode after the session close code has completed. --------------------------------------------------------------------------- ATTENTION! Do NOT reply to this email! To reply, use the web interface found at http://bugs.php.net/?id=10775&edit=2

« previous php.dev (#56968) next »