Title: critical error warning
Last modified: June 25, 2026

---

# critical error warning

 *  Resolved [lbdesign](https://wordpress.org/support/users/lbdesign/)
 * (@lbdesign)
 * [1 week, 3 days ago](https://wordpress.org/support/topic/critical-error-warning-3/)
 * My site config is set to the max of 256MB
 * I received this error:
 * WordPress has a built-in feature that detects when a plugin or theme causes a
   fatal error on your site, and notifies you with this automated email.
 * In this case, WordPress caught an error with one of your plugins, Debug Log Manager.
 * Error Details
   =============An error of type E_ERROR was caused in line 498 of
   the file /home/sites/42b/f/f0b059d7a5/public_html/wp-content/plugins/debug-log-
   manager/classes/class-debug-log.php. Error message: Allowed memory size of 268435456
   bytes exhausted (tried to allocate 78607544 bytes)

Viewing 3 replies - 1 through 3 (of 3 total)

 *  Plugin Author [Bowo](https://wordpress.org/support/users/qriouslad/)
 * (@qriouslad)
 * [1 week, 3 days ago](https://wordpress.org/support/topic/critical-error-warning-3/#post-18948122)
 * [@lbdesign](https://wordpress.org/support/users/lbdesign/) thank you for reporting
   this. On which version of Debug Log Manager (DLM) are you?… can you share a screenshot
   of the DLM dashboard, specifically the settings at the bottom?
 *  Thread Starter [lbdesign](https://wordpress.org/support/users/lbdesign/)
 * (@lbdesign)
 * [1 week, 3 days ago](https://wordpress.org/support/topic/critical-error-warning-3/#post-18948441)
 * I’m sorry, I uninstalled it. But it was the current version.
 *  Plugin Author [Bowo](https://wordpress.org/support/users/qriouslad/)
 * (@qriouslad)
 * [1 week, 2 days ago](https://wordpress.org/support/topic/critical-error-warning-3/#post-18948521)
 * [@lbdesign](https://wordpress.org/support/users/lbdesign/) I understand. Based
   on your original report and that you were using v2.5.1 (latest at the time), 
   I’ve done an investigation and the error appears to be valid and can indeed trigger
   memory exhaustion when the debug.log file is substantially large. I’ve just released
   v2.5.2 that contains a fix for it. Please download and install manually for now:
   [https://downloads.wordpress.org/plugin/debug-log-manager.2.5.2.zip](https://downloads.wordpress.org/plugin/debug-log-manager.2.5.2.zip).
   New wp.org policy puts a 24 hour delay before “update is available” notices starts
   appearing in your site.

Viewing 3 replies - 1 through 3 (of 3 total)

You must be [logged in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fcritical-error-warning-3%2F%3Foutput_format%3Dmd&locale=en_US)
to reply to this topic.

 * ![](https://ps.w.org/debug-log-manager/assets/icon-256x256.png?rev=2783658)
 * [Debug Log Manager - Conveniently Monitor and Inspect Errors](https://wordpress.org/plugins/debug-log-manager/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/debug-log-manager/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/debug-log-manager/)
 * [Active Topics](https://wordpress.org/support/plugin/debug-log-manager/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/debug-log-manager/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/debug-log-manager/reviews/)

 * 3 replies
 * 2 participants
 * Last reply from: [Bowo](https://wordpress.org/support/users/qriouslad/)
 * Last activity: [1 week, 2 days ago](https://wordpress.org/support/topic/critical-error-warning-3/#post-18948521)
 * Status: resolved