Bug #13554 Updated: Storing complex object as session variable makes apache go beserk
| From: | mgrommet at hotmail dot com | Date: | Fri, 05 Oct 2001 07:46:35 +0000 |
| Subject: | Bug #13554 Updated: Storing complex object as session variable makes apache go beserk | ||
| References: | 1 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-67322@lists.php.net to get a copy of this message | ||
ID: 13554
User updated by: mgrommet@hotmail.com
Reported By: mgrommet@hotmail.com
Status: Open
Bug Type: Session related
Operating System: Redhat Linux
PHP Version: 4.0.6
New Comment:
It should also be noted that I dont see this problem with much smaller / less complex objects.
Previous Comments:
------------------------------------------------------------------------
[2001-10-05 02:54:51] mgrommet@hotmail.com
Before this, I've started the session, and have included the file defining the Test class.
session_register("testCache");
if(!isset($testCache))
{
$testCache = new Test($testid);
echo "Loading non cached...";
}
It should be noted that an instantiated Test object is really pretty darn hefty and contains arrays
of objects in its attributes with many methods. Total footprint is probably around 150k or so.
The first time this code is executed, testCache is empty
and is created within the body of the if statement
The second time (reload the page for instance) it causes the apache process servicing the request to
gobble up insane amounts of memory. As far as I can tell, apache will never respond back. On the
reload, the session variable should be set
------------------------------------------------------------------------
Edit this bug report at http://bugs.php.net/?id=13554&edit=1