You may have gotten my test version I was playing around with. (Adding a new feature to check/delete the x_logs DB table). This new feature does use a lot of RAM if your x_logs table is huge (which it probably is!) Mine usually gets over 10,000 rows in a week or so. You can try again by manually going to this table and truncating it using phpmyadmin, then reinstall the deleted records manager module. I am currently working on a daily daemon run hook that will automatically truncate this huge log file and keep the last x entries.
I'll restore the currently released package for you.
I'll restore the currently released package for you.