Debug This –> PHP –> Variables Throws Out Of Memory Error?
-
Debug This seems great and I can see a lot of the reports no problem, but when I tried to view PHP –> Variables I get a Fatal Error: Out of Memory.
Here is the full error:
( ! ) Fatal error: Out of memory (allocated 327614464) (tried to allocate 158564352 bytes) in /var/www/html/wp-includes/functions.php on line 3721
Call Stack
# Time Memory Function Location
1 0.0008 367680 {main}( ) …/index.php:0
2 0.0011 367968 require( ‘/var/www/html/wp-blog-header.php’ ) …/index.php:17
3 0.9539 7349280 require_once( ‘/var/www/html/wp-includes/template-loader.php’ ) …/wp-blog-header.php:19
4 1.7763 7668216 include( ‘/var/www/html/wp-content/plugins/debug-this/inc/debug-template.php’ ) …/template-loader.php:74
5 9.4376 325557744 ob_get_contents ( ) …/debug-template.php:29
6 9.4384 325557824 shutdown_action_hook( ) …/load.php:0
7 9.4384 325557824 do_action( ) …/load.php:677
8 9.4385 325558576 WP_Hook->do_action( ) …/plugin.php:453
9 9.4385 325558576 WP_Hook->apply_filters( ) …/class-wp-hook.php:323
10 9.4385 325559704 wp_ob_end_flush_all( ) …/class-wp-hook.php:298
11 9.4385 325559704 ob_end_flush ( ) …/functions.php:3721Any ideas?
Thanks!
Dave
-
Hi Dave,
Thanks for providing the error message. Debug This is not perfect. ??
That report prints out all the variables in the current scope, including the WordPress actions and filters.
It buffers the entire page in order to capture all the actions and filters from WordPress startup to shutdown.
It then stores that buffer in a variable in order to insert it into the report. That’s where it runs out of memory.
158564352 ~= 151 MB. That’s a huge report and probably not very helpful unless you’re looking for a specific variable in a plugin or theme with front-end output on whatever page you ran the report. If so, there are better techniques.
Most of those variables are available in other reports.
- The topic ‘Debug This –> PHP –> Variables Throws Out Of Memory Error?’ is closed to new replies.
