• This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn more.

XF 1.1 Fatal error: Out of memory

IcEWoLF

Well-known member
#1
Fatal error: Out of memory (allocated 6029312) (tried to allocate 84 bytes) in /home/xxxxxxxx/xxxxxxxxxx/library/Zend/Db/Statement/Mysqli.php on line 304

I've been getting this problem time to time.

My host set my php limit to 512mb

Not sure what else to do here.
There are no threads awaiting for moderation.
 

IcEWoLF

Well-known member
#4
Well here is the reply my host gave me:

This is not advised as it will allow PHP Processes to consume all of your virtual machines RAM. Keeping the memory limit in tact prevents a single process from taking down the entire virtual machine. It will lead to more instability.
 

Mike Edge

Well-known member
#5
It should be fine. We use -1 and then control each account at a package level via Cloud Linux.

How much RAM does your VPS have?
 

Mike

XenForo developer
Staff member
#8
This isn't a memory_limit thing. It's an out of memory error - as in, PHP couldn't allocate memory. In this case, after about 6MB. I'm not going to say you need more memory, but you may need to tune the memory usage of various services.
 

CTXMedia

Formerly CyclingTribe
#9
Fatal error: Out of memory (allocated 6029312) (tried to allocate 84 bytes) in /home/xxxxxxxx/xxxxxxxxxx/library/Zend/Db/Statement/Mysqli.php on line 304
Where do you see this error / what are you (your members) doing when it happens?

Does it happen only in the ACP or during a particular task / request?
 

WSWD

Well-known member
#10
If the memory limit was previously 512mb, increasing it to 1GB or even -1 shouldn't make a bit of difference. It's happening after 6mb.

Why don't you post the contents of your php.ini file and we can go from there. Something doesn't sound right.
 

WSWD

Well-known member
#12
Thanks,

Try going to your httpd.conf file, and looking for RLimitMEM. Remove the line (or comment it out) if it exists, restart Apache and see if that does the trick. Your php.ini generally looks normal.
 

DarkGizmo

Active member
#14
Disable that mod then and see if that fixes your problems, that's kind of the obvious way of troubleshooting it and knowing for sure if that's the mod's fault or not.
 

IcEWoLF

Well-known member
#15
Disabled the mod and did not have an issue all day long.
Re-enabled the mod and today I've been having issues, so something with this mod is causing the memory issue.
 

IcEWoLF

Well-known member
#16
Update, I disabled the mod and after a day, this issue is still happening, we disabled all the mods but no fix yet, we even were moved to a new node and the issue still persists.
I am running out of options.
 

Jake Bunce

XenForo moderator
Staff member
#19
https://drupal.org/node/463234#comment-1794502
> https://drupal.org/node/371789#comment-1334640

It was particularly insightful that there were TWO DIFFERENT types of memory limits: an Apache limit and a PHP limit.
I got an answer saying that the cause is that I have hit one of Apache's limits, which are:

RLimitMEM 83886080 104857600 (which covers all Apache memory needs)
RLimitCPU 150 200
RLimitNPROC 25 30
I think WSWD may be correct. This error is not from PHP's memory_limit, so it may be from Apache:

Try going to your httpd.conf file, and looking for RLimitMEM. Remove the line (or comment it out) if it exists, restart Apache and see if that does the trick. Your php.ini generally looks normal.
Your host needs to check this for you. You cannot access httpd.conf without root access.
 

IcEWoLF

Well-known member
#20
Thanks guys, I submitted the ticket , unfortunately the host is being terrible as of late since it's takes them nearly a day to reply to a ticket...time for me to consider looking for a new vps server provider soon. :mad: