Still generating oversized debug.log file that overwhelms available memory

[thompsonpaul]

Running V2.5.2 and the plugin is still generating a log file over 1.2GB on a couple of problematic sites.

This causes memory exhaustion errors and blocks site login if the debug widget is enabled in the WP dashboard.

I know you've been working on a process to limit log size to avoid this issue - wanted to let you know it's still occurring.

WP 7.04
DBL V2.5.2
PHP 8.3.33 Memory Limit 384MB

[qriouslad]

@thompsonpaul thank you for reporting this. Will investigate once I find the time for it.

[thompsonpaul]

Following up with an example for reference. The site admin white-screened again with the following:

An error of type E_ERROR was caused in line 237 of the file
/redacted/public_html/wp-content/plugins/debug-log-manager/classes/class-log-trimmer.php
Error message: Allowed memory size of 402653184 bytes exhausted (tried
to allocate 301989896 bytes)

The debug log had grown to 374MB

Obviously I have a problem with all the deprecation warnings that are expanding the log so fast, but it seems like the log tailing tries to happen on login because the dashboard widget was enabled? Maybe it could be run via a cron job instead?