Error: allowed memory size exhausted

  • Resolved kham7236

    (@kham7236)


    6 months, 1 week ago

    I had a critical error when I attempted to log into WordPress. I received this error in email:

    “An error of type E_ERROR was caused in line 471 of the file /chroot/home/a63d83d6/91bf8a52f2.nxcli.io/html/wp-content/plugins/debug-log-manager/classes/class-debug-log.php. Error message: Allowed memory size of 2147483648 bytes exhausted (tried to allocate 900247712 bytes)”

    My hosting company suggested contacting this forum because of the excessive usage. I would appreciate your help in resolving this. I have currently deactivated DLM so I can work in WordPress. (The website is working fine for visitors.)

    WordPress version 6.8.3

    Active theme: Kadence (version 1.2.28)

    Current plugin: Debug Log Manager (version 2.4.3) PHP version 8.1.33

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Bowo

    (@qriouslad)

    6 months ago

    @kham7236 it’s probably because you leave DLM error logging enabled and your site is generating a lot of errors and the debug.log file is growing too large, larger than what is allocated to your WP app. If you deactivate and reactivate DLM, the debug.log file should be automatically reset (emptied out) and you can use DLM again.

    Thread Starter kham7236

    (@kham7236)

    6 months ago

    @qriouslad – Thanks for the quick response. After deactivating and reactivating, I was able to access everything in my WP dashboard; but when I clicked on the debug log I got the critical error again:

    “An error of type E_ERROR was caused in line 471 of the file /chroot/home/a63d83d6/91bf8a52f2.nxcli.io/html/wp-content/plugins/debug-log-manager/classes/class-debug-log.php. Error message: Allowed memory size of 2147483648 bytes exhausted (tried to allocate 1739503888 bytes)”

    Would it be worth a try to delete DLM, then reinstall it? Or is there something else I can do?

    Plugin Author Bowo

    (@qriouslad)

    6 months ago

    @kham7236 please deactivate DLM, go to /wp-content/uploads/debug-log-manager/ and delete the debug.log file(s) there, and reactivate DLM. Then turn on logging again. That should give you a fresh start. Will likely need to implement some sort of auto-purge mechanism when the size of the debug.log file grows too large.

    Plugin Author Bowo

    (@qriouslad)

    5 days, 22 hours ago

    @kham7236 in the next release, v2.5.0, there will be a mechanism added to limit the size of debug.log file so it does not grow larger than available memory. Thanks again for reporting this issue in the first place.

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

You must be logged in to reply to this topic.