ID: 48434 Updated by: scott...@php.net Reported By: busia at tiscali dot it -Status: Open +Status: Bogus Bug Type: Feature/Change Request PHP Version: 5.3.0RC2 New Comment:
Sorry, but your problem does not imply a bug in PHP itself. For a list of more appropriate places to ask for help using PHP, please visit http://www.php.net/support.php as this bug system is not the appropriate forum for asking support questions. Due to the volume of reports we can not explain in detail here why your report is not a bug. The support channels will be able to provide an explanation for you. Thank you for your interest in PHP. It's already there. memory_get_usage() and memory_get_usage(true) Previous Comments: ------------------------------------------------------------------------ [2009-05-30 09:33:08] busia at tiscali dot it Description: ------------ You said me (#48368) that unset != free. The memory can remain occupied also after I unset an array, that memory is reused when I set a new variable and, for this reason, it's not a leak. Ok, now it's clear but a problem remains: how can I optimize my code when I cannot see the php internal memory use? I need a function like: memory_get_usage() - memory_allocated_but_usable_for_newly_created_variables(); Setting a variable and seeing that memory use don't change make scripts impossible to optimize. Thanks ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=48434&edit=1
