Memory exhausted error

  • Resolved vikp

    (@vikp)


    2 years, 1 month ago

    I’m getting memory exhausted errors in my test and production site . When checking php-slow query log I could see lots of errors like below:

    script_filename = /index.php
[0x00007f8fcba182e0] mysqli_query() /wp-includes/wp-db.php:2169
[0x00007f8fcba18270] _do_query() /wp-includes/wp-db.php:2058
[0x00007f8fcba18190] query() /wp-content/plugins/query-monitor/classes/QM_DB.php:54
[0x00007f8fcba180d0] query() /wp-includes/wp-db.php:2798
[0x00007f8fcba18010] get_col() /wp-includes/class-wp-query.php:3129
[0x00007f8fcba17860] get_posts() /wp-includes/class-wp-query.php:3586
[0x00007f8fcba177f0] query() /wp-includes/class-wp-query.php:3718

    Strange thing is I already deactivated Query monitor plugin few months ago, but errors pointing to QM_DB.php in in query monitor plugin…
    like above i could see lots of errors with different files names, but in all query-monitor/QM_DB is common.

    Any idea why this happening even we uninstalled the plugin ?

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author John Blackbourn

    (@johnbillion)

    WordPress Core Developer

    No idea, sorry. Are those logs coming from another site where QM is active?

    Thread Starter vikp

    (@vikp)

    Hi John,

    Thanks for the quick reply.
    I could see that a symlink from wp-content/db.php to /query-monitor/classes/QM_DB.php .

    Since I’m not using the QM plugin in test and production server, I deleted this symlink, now error not showing /query-monitor/classes/QM_DB.php path.

    If I don’t delete this wp-content/db.php file, will the Query Miniotr plugin continue to function as if it were activated? Is it take more memory and other resources?

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Memory exhausted error’ is closed to new replies.