#13437 [Com]: PHP cores on exit; memory deallocation problem?

ID: 13437 Comment by: morgan at mindviz dot com Reported By: dshadow at zort dot net Status: No Feedback Bug Type: Reproducible crash Operating System: Linux & Solaris PHP Version: 4.1.1 New Comment: I am currently doing some work with php for a server application. At times I will read in roughly 1-2MB of data and unserialize it, at this point the memory usage in top will spike up to 10MB and sit there indefinitely. I have run the program over and tested without the unserialize being used, still loading the data being into a string, and no jump to 10MB. Is there some memory leak issue in the unserialize routine? This is pretty critical for me, everytime I call unserialize on the large set of data loaded in it will jump a bit more from the 10MB, and keep doing that until my entire system is exhausted of memory. At this point I am considering writing my own unserialize routine to see if it helps. I have tried this with version 4.2.3, 4.3.1 and 4.3.2 and get the same results. Any help would be great, thanks Previous Comments: ------------------------------------------------------------------------ [2002-11-27 11:04:47] kennon at retirequickly dot com This same behavior is happening to me using PHP version 4.1.2. I have a script that has several very large arrays (~200MB each), and after the script is finished, the php process begins to max out the processor, and can take hours to finish. Sometimes the script will stop with a "Maximum execution time of 30 seconds in file Unknown" error, even though I have the max time at 1 hour. I even tried to manually unset() the large variables, and while the unset() calls appear to be successful, the same behavior is still present. This feels like exactly the same bug, but I can provide a backtrace if necessary. I'm running Redhat 7.3 on a dual processor intel system. Thanks! ------------------------------------------------------------------------ [2002-08-05 01:00:12] php-bugs at lists dot php dot net No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open". ------------------------------------------------------------------------ [2002-07-04 16:18:26] eru@php.net Thank you for taking the time to report a problem with PHP. Unfortunately your are not using a current version of PHP -- the problem might already be fixed. Please download a new PHP version from http://www.php.net/downloads.php If you are able to reproduce the bug with one of the latest versions of PHP, please change the PHP version on this bug report to the version you tested and change the status back to "Open". Again, thank you for your continued support of PHP. ------------------------------------------------------------------------ [2002-02-04 16:21:13] edink@php.net On user request status => open ------------------------------------------------------------------------ [2002-02-04 16:06:43] dshadow at zort dot net This problem still happens with PHP 4.1.1. The edit submission page does not permit me to reopen bugs; I can't change that status. Can someone else please reopen this? Thanks. ------------------------------------------------------------------------ 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/13437 -- Edit this bug report at http://bugs.php.net/?id=13437&edit=1