• Resolved Gμ?rD???

    (@guardian74)


    I took a look at @jame’s pinned post and saw a reference to “sql” issues at the bottom and they were helpful overall but it still didn’t address my particular issue so I wanted to find out what is going on and how I can resolve it.

    First off, the error:

    Fatal error: Out of memory (allocated 134062080) (tried to allocate 274432 bytes) in /wp-includes/wp-db.php on line 1811

    Second a look at that line:

    $this->result = mysqli_query( $this->dbh, $query );

    This led to me believe it has something to do with the rest of the mysqli issues that @james referred to but I am not sure exactly how this is applying to me given the error is about memory allocation.

    The general thinking would be its not getting enough memory, but here is the problem, I have 2 GB dedicated RAM on this installation, there is NOTHING in the world that can overflow that limit in MY setup. Secondly, the amount of memory showing as allocated and what little its failing on, makes no sense to me. Especially that simply F5 or reloading the page moves on.

    The issue occurs on the backend, on the front end, and especially on post editing/publishing. Before I read about the removal of the “hiding” suggesting that the problems were there before just not visible, ok, I can get behind that because I tested (before reading that) by cloning the site, db and all and simply rolling back the version to one before 4.5.3 because that’s when it started happening. But since its completely killing the render, my guess is its more than just a hiding issue, thoughts?

    So anyone know what’s going on here? My site is up to date, my plugins, themes and everything are up to date, my db is pruned, regularly and optimized, so its not that. The server is fast, so is the MySQL db server. No other app connects to that DB. I am at my wits end, as I can’t narrow it down to what the problem is, any assist would be greatly appreciated, especially if someone has gone down the path outlined by @james and has discovered a solution.

    TIA.

Viewing 6 replies - 16 through 21 (of 21 total)
  • Thread Starter Gμ?rD???

    (@guardian74)

    Yes for the moment it seems the issue has resolved, now just the wait and see game to make sure it doesn’t come up again. While it seems it was the culprit, there is the chance it was a coincidence of timing and there is something else but if there is, then it should surface with time, I will update everyone here – that way the history of everything can be preserved in a quasi-timeline.

    Thread Starter Gμ?rD???

    (@guardian74)

    @james, thank you for the journey and if you have any thoughts on the other issue, would love to hear it there where it will be contextually more appropriate. Thanks.

    Moderator James Huff

    (@macmanx)

    You’re welcome!

    Let us know how it turns out over time. ??

    No thoughts on the iThemes Security thing myself, I haven’t used them recently.

    Thread Starter Gμ?rD???

    (@guardian74)

    Will do, you can count on it, thanks.

    That’s ok, there is always a chance observation will trigger something, so if you think of something, share.

    Moderator James Huff

    (@macmanx)

    Sure will. ??

    Thread Starter Gμ?rD???

    (@guardian74)

    @james, just wanted to fulfill the promise to update you on this. Since we last left off on this, I have not had any page timeouts, white pages, or missed posts (except 1 about 2 weeks ago and I am pretty sure that was just a convergence of coincidence that probably multiple jobs clashed and one took a knee, not earth shattering, just SOP)

    As for the load time, I have found that on Edge, its very snappy less than 2 seconds, on Firefox it averages about the same, and on Chrome its most inconsistent but still below 3 seconds. On Mobile Chrome however, nearly instant – go figure.

    That’s it bud, just wanted to see it through. Cheers.

Viewing 6 replies - 16 through 21 (of 21 total)
  • The topic ‘Fatal error: Out of memory’ is closed to new replies.