Debug still too big

Hello again,

I am creating a new topic because it seems lost if I added another answer in the old one…

What is the issue? We have debug options set off. However the file size is over 40 MB (Debug file size: 40,884,812.57 KB (40,884.81 MB).). Is it possible to disable it?? This is what I see if I click view debug file:

2019-07-02 07:14:52 CEST (INFO): deleteOldRedirectsCron. Old captured URLs removed: 0, Old automatic redirects removed: 0, Old manual redirects removed: 0, Old log lines removed: 0, New log size: 9.27MB, Duplicate rows deleted: 1, Debug file size limited: true, Admin email notification option turned off., Permlink cache rows updated: 0, User initiated: false

Credits: 404 Solution is maintained by Aaron J.
Plugin version: 2.21.1, PHP: 7.2.19-1+ubuntu16.04.1+deb.sury.org+1, WordPress: 5.2.2, MySQL: 5.5.5, WP Memory Limit: 40M, mbstring Extension: true

I can see in Temp folder that there is also abj404_debug.txt_old.txt which has 40 MB. In my opinion the debug is running all the time and is not stopped even though we do not have it enabled. And when it reaches the limit 40 MB, then it shows php errors in our logs and creates a new file…? And what is even more strange, even though the file shows 40 MB, I have stopped copying the file after 260 MB. The debug files are quite strange and should not be created at all.

Below is also our php errors log:
Jul 02, 01:50:31

Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 20480 bytes) in /home/keengamer/public_html/wp-content/plugins/404-solution/includes/Logging.php on line 110

Jul 02, 01:50:30

Warning: implode(): Invalid arguments passed in /home/keengamer/public_html/wp-content/plugins/404-solution/includes/Functions.php on line 72

Jul 02, 01:49:17

Fatal error: Unknown: Cannot use output buffering in output buffering display handlers in Unknown on line 0

Regards,
Karel