Wordfence conflict

This isn’t so much a conflict as it is a general issue with debugging plugins that collect data (eg. Query Monitor) and plugins that perform long running actions or perform a large number of database queries like site scans, backups, content analysis, etc (eg. Wordfence).

There’s not much that Query Monitor can do in this situation as it depends entirely on how large your site is, how much memory it has available, how many queries run during the scan, and other factors.

In the future I hope to add a form of memory limiting to the data that QM collects, but it’s not a high priority at the moment.

Thanks.

So, if I understand correctly, I can’t leave them both active, as the scheduled Wordfence scans would fail?

Isn’t there a way to use hooks for deactivating Query Monitor when a Wordfence scan begins and re-activating it when the scan is done?

There are some ways to prevent QM from logging its data but it needs to be done very early in the load process.

You can try defining the SAVEQUERIES constant as false.

You can try defining the QM_DISABLED constant as true.

The folks at Wordfence might be able to set one of these before a scan runs.

Thanks

@asafm7, did you try increasing your WP memory limit? That’s the thing that jumps immediately to mind when reading your problem description. Try something like this in your wp-config.php at the WP root directory:

define('WP_MEMORY_LIMIT', '256M');