XF 1.5 Fatal Error: Allowed memory size of 671088640 bytes exhausted (tried to allocate 786432 bytes)

sdrothrock

sdrothrock

Member
How can I track down what's causing this? It happens over a dozen times a day, usually when users are viewing nodes or the front page.

Code: 
Server Error Log
Error Info
ErrorException: Fatal Error: Allowed memory size of 671088640 bytes exhausted (tried to allocate 786432 bytes) - library/XenForo/Template/Abstract.php(265) : eval()'d code:1752
Generated By: Unknown Account, 54 minutes ago
Stack Trace
#0 [internal function]: XenForo_Application::handleFatalError()
#1 {main}
Request State
array(3) {
  ["url"] => string(33) "https://myforum.com/"
  ["_GET"] => array(0) {
  }
  ["_POST"] => array(0) {
  }
}
 
Sort by date Sort by votes
Unfortunately, this is difficult to debug unless you can reproduce it with consistency. I'd have to guess this is add-on related, though it could also be related to your custom style. Debugging may require disabling add-ons one-by-one to see if/when the errors stop.
 
Upvote 0 Downvote
xenfans said:
PHP memory issues, have you tried increasing the available memory for php in the config (of php)
Click to expand...

Seems dubious. There shouldn't be any reason for the forum to be sucking up 700 MB of RAM to show a node list.

Mike said:
Unfortunately, this is difficult to debug unless you can reproduce it with consistency. I'd have to guess this is add-on related, though it could also be related to your custom style. Debugging may require disabling add-ons one-by-one to see if/when the errors stop.
Click to expand...

Disabling add-ons one-by-one seems a bit prone to error.. any other ideas, since you said "may require"? I'm quite comfortable with the shell; I just don't know my way around PHP.
 
Upvote 0 Downvote
sdrothrock said:
640 MB AKA 671088640 bytes.
Click to expand...
Just saying, it can be set to 32M and still report that 640M has been exhausted. As per many Google results.
It's local value is not being overwritten by say Apache as a master value (or something like that)? Try force overwriting it by updating .htaccess with something like php_value memory_limit 1024M or whatever you think is reasonable to use.
In the CLI you can find the .log files under /var/log usually, perhaps you can use: tail -F file.log
and run the frontpage of the forum and see where it runs into the error specifically. You could also try running the site in debug mode and load the ?debug=1 in the url and see when it errors, if it discloses where it errors on that page if you get lucky.

Try reproducing it with turning off some add-ons from the admin.php > list of add-ons, that aren't really essential to the site and see if you can reproduce the issue, perhaps try making a default theme and run that, see if it fixes it.

It seems to occur when xenforo throws stuff through eval(); so perhaps it's trying to cache templates to the disk, or one of those sort of situations (maybe mike can tell us which obvious cases uses eval)
 
Upvote 0 Downvote
xenfans said:
It's local value is not being overwritten by say Apache as a master value (or something like that)? Try force overwriting it by updating .htaccess with something like php_value memory_limit 1024M or whatever you think is reasonable to use.
Click to expand...

It's not in nginx (I don't use apache). AFAIK nginx doesn't affect it like Apache does.

xenfans said:
In the CLI you can find the .log files under /var/log usually, perhaps you can use: tail -F file.log
Click to expand...

Happen to know what the log is called? Nothing stands out as being xenforo-related.

xenfans said:
and run the frontpage of the forum and see where it runs into the error specifically. You could also try running the site in debug mode and load the ?debug=1 in the url and see when it errors, if it discloses where it errors on that page if you get lucky.
Click to expand...

Tried that, the error is very intermittent and I couldn't get it after 100 refreshes... but we have an average of 300-400 users on at a time, so it's fairly common for a user to see it, I'm guessing.
 
Upvote 0 Downvote
It is in a template, so serving the templates from files may help pinpoint it a little bit more (the template itself and then tracing into the actual compiled line), but the problem is that the issue may not be with the line in question -- that's just what's tipping it over, so it could be something earlier using a huge amount of memory. That said, it's trying to allocate over 700k here, so that would imply it has a large chunk of data involved on this line.
 
Upvote 0 Downvote
Mike said:
It is in a template, so serving the templates from files may help pinpoint it a little bit more (the template itself and then tracing into the actual compiled line), but the problem is that the issue may not be with the line in question -- that's just what's tipping it over, so it could be something earlier using a huge amount of memory. That said, it's trying to allocate over 700k here, so that would imply it has a large chunk of data involved on this line.
Click to expand...

I gave that a shot, took a while for the error to show up, but had no more information than before... unless you meant to look for the actual compiled line, which I realize now you just said! Where could I find the file for the template in question?

Mike said:
That said, it's trying to allocate over 700k here, so that would imply it has a large chunk of data involved on this line.
Click to expand...

Just to make sure I'm not misunderstanding the nature of the error -- isn't this actually trying to allocate over 640 MB? If it's actually 700k and there's a problem in my memory settings, I'm not too worried about it...
 
Upvote 0 Downvote
Actually, it was slightly different:

Code: 
Server Error Log
Error Info
ErrorException: Fatal Error: Allowed memory size of 671088640 bytes exhausted (tried to allocate 72 bytes) - library/XenForo/Template/Abstract.php:591
Generated By: trombone, Today at 3:19 AM
Stack Trace
#0 [internal function]: XenForo_Application::handleFatalError()
#1 {main}
Request State
array(3) {
  ["url"] => string(33) "https://myforum.com/"
  ["_GET"] => array(0) {
  }
  ["_POST"] => array(0) {
  }
}
 
Upvote 0 Downvote
sdrothrock said:
Just to make sure I'm not misunderstanding the nature of the error -- isn't this actually trying to allocate over 640 MB? If it's actually 700k and there's a problem in my memory settings, I'm not too worried about it...
Click to expand...
The example in question was a failed allocation of over 700KB of memory due to hitting the memory limit. That's what I meant by the "tipping over" comment.

The new backtrace is actually a really good example: it's a 72 byte allocation that triggered the limit. We unfortunately won't have any clue where the other 640MB of memory went. And given that there's no obvious reproduction case, that will make debugging this virtually impossible unfortunately. Because PHP doesn't give very useful error messages here, it really needs something to allow it to be triggered consistently so it can be worked through methodically.
 
Upvote 0 Downvote
Mike said:
The example in question was a failed allocation of over 700KB of memory due to hitting the memory limit. That's what I meant by the "tipping over" comment.

The new backtrace is actually a really good example: it's a 72 byte allocation that triggered the limit. We unfortunately won't have any clue where the other 640MB of memory went. And given that there's no obvious reproduction case, that will make debugging this virtually impossible unfortunately. Because PHP doesn't give very useful error messages here, it really needs something to allow it to be triggered consistently so it can be worked through methodically.
Click to expand...

I actually found a user who triggers this every time he tries to log in... any ideas about things I can do? Thinking about enabling debug mode and logging in as him.
 
Upvote 0 Downvote
Turning debug mode on, sadly, just gave the same output as what was logged in the admin panel.

Tried increasing the memory limit, and interestingly enough, it went over by the same amount both times.

Before:

Code: 
Server Error Log
Error Info
ErrorException: Fatal Error: Allowed memory size of 671088640 bytes exhausted (tried to allocate 786432 bytes) - library/XenForo/Template/Abstract.php(265) : eval()'d code:1752
Generated By: a user, 6 minutes ago
Stack Trace
#0 [internal function]: XenForo_Application::handleFatalError()
#1 {main}
Request State
array(3) {
  ["url"] => string(33) "https://forum.replica-watch.info/"
  ["_GET"] => array(0) {
  }
  ["_POST"] => array(0) {
  }
}

After:

Code: 
Server Error Log
Error Info
ErrorException: Fatal Error: Allowed memory size of 713031680 bytes exhausted (tried to allocate 786432 bytes) - library/XenForo/Template/Abstract.php(265) : eval()'d code:1752
Generated By: a user, 2 minutes ago
Stack Trace
#0 [internal function]: XenForo_Application::handleFatalError()
#1 {main}
Request State
array(3) {
  ["url"] => string(33) "https://forum.replica-watch.info/"
  ["_GET"] => array(0) {
  }
  ["_POST"] => array(0) {
  }
}

Notice that both tried to allocate 786432 bytes despite the limit being higher...
 
Upvote 0 Downvote
If you turn on templates as files, can you get that error within the template?

It certainly looks like some sort of huge/infinite loop in a template.
 
Upvote 0 Downvote
You must log in or register to reply here.

Similar threads

soloarquitectura
Confirmed Export user list: Fatal error: Allowed memory size
Replies
1
Views
40
MentaL
MentaL
Jaxel
  • Question Question
XF 2.3 Constant Fatal Error: Allowed memory size exhausted errors since upgrade
Replies
5
Views
104
Jaxel
Jaxel
rickhz
Duplicate ErrorException: Fatal Error: src/XF/Mvc/Entity/Entity.php:1858
Replies
1
Views
50
Jeremy P
Jeremy P
rickhz
  • Question Question
XF 2.3 ErrorException: Fatal Error: Keep getting these since upgrade
Replies
2
Views
79
rickhz
rickhz
Alexander.
  • Question Question
XF 2.2 ErrorException: Fatal Error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 81920 bytes) src/XF/Db/Mysqli/Statement.php:127
Replies
8
Views
1K
Neilski
N
Back
Top Bottom