Description: ------------ Var_dump cannot dump large arrays containing objects because the memory runs out during the preg_match_all() function. I have a solution for that: In my case, there are many variables in the 'ignore_list' parameter. These to-be-ignored parameters should be removed before calling preg_match_all()

Hey Michael, I don't suppose you've got some small test cases? Or if you've tried newer PHP versions?

Hello Version 5.1.6 should be really very new and I am sorry, I have no test scenario ready. But I have somewhat like a recursive dependency between two objects, both having references to each other. This is causing the memory leak. In the ignore parameters I am using class names of these objects referencing to each one but this doesn't help because ignoring classes isn't done before calling var_dump(), that's the problem. Cheers Michael H.

I agree with Daniel, version 5.1.6 was released on 24-Aug-2006, that is to say almost two years ago ! Anyway, could you please check Bug #3965 (Unable to dump big size Object) and go through proposed solutions to see if it can solve your problem. Regards

I agree with Daniel, version 5.1.6 was released on 24-Aug-2006, that is to say almost two years ago ! Anyway, could you please check Bug #3965 (Unable to dump big size Object) and go through proposed solutions to see if it can solve your problem. Regards

Hello guys Thank you for your support. Well, the hosting provider will upgrade to PHP 5.2.3 :) About the bug #3965 , I did some research and used this pseudocode for the big variable $inputRegistry: // lots of processing echo 'A: ' . memory_get_usage(); ob_start(); var_dump($inputRegistry); $result = ob_get_contents(); ob_end_clean(); echo 'B: ' . memory_get_usage(); echo 'C: ' . strlen($result); echo 'D: ' . strlen(serialize($result)); exit; The output was: A: 9577400 B: 43640296 C: 34062894 D: 34062908 As you can see, $inputRegistry is a very big variable with lots of recursion inside. Hope I could help you to locate the problem. Thank you for your help!! M. Heuberger

Thank you for taking the time to report a problem with PHP. Unfortunately you 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 PEAR. fixed