X-Cart forums

[kokeyuk1]

ERROR: "Includes\ErrorHandler::FATAL_ERROR" (code 2)

Allowed memory size of 268435456 bytes exhausted (tried to allocate 16777216 bytes)

We are getting this error message on our site. Nothing is currently being uploaded or changed etc.

What is this error and how can we fix it?

Thanks in advance.

[Ksenia]

Hi!
What version and Edition of X-Cart are you using? Please add it to your signature.

Also, it's always useful ro describe the issues you face in as many details as possible: where do you see the problem, what you did before it appeared and so on.

Originally Posted by kokeyuk1

ERROR: "Includes\ErrorHandler::FATAL_ERROR" (code 2)

Allowed memory size of 268435456 bytes exhausted (tried to allocate 16777216 bytes)
What is this error and how can we fix it?

This error means that the server ran out of memory for some reason. Or, probably there's some memory, but it can not be used because of memory_limit value set in php.ini

Thus the easiest way to fix it is to contact your hosting provider and ask to increase the memory limit.

[AAPLA]

I'm hitting the same error when trying to enable 'Clean URLs'. The current limit I have set is: memory_limit = 128M

What do you recommend setting the memory limit to?

[tony_sologubov]

The preferable memory_limit is more than 256M.

kokeyuk1 how many products do you have? Anyway, increasing memory limit to 512M-1024M should help.

Tony.

[AAPLA]

My provider updated the memory limit to over 256MB as recommended, but the issue remains. The error page layout changed a little now, but seems to be the same error message.

I attached a screenshot of the error and included the text below.

ERROR: "Includes\ErrorHandler::FATAL_ERROR" (code 2)
Call to a member function map() on a non-object

Any advice on what else it might be? So far I'm only hitting this error when I try to enable Clean URLs from the Environment page.

[tony_sologubov]

Hi AALPA!

This problem is caused by the fact that you are missing a record with name "clean_url_flag" in xc_config table of your X-Cart.

Our support team can help you to fix the problem and find its origin. Just drop us a message at support@x-cart.com

[chamitrail@gmail.com]

I do have the same issue. I quadrupled my memory_limit in php.ini file. Since this is an installation of the sample XCart I don't think the issue is a missing record. But after doing all these my X-Cart's front end still doesn't work.

The followin error.....

An error occurred in your store.
ERROR: "Includes\ErrorHandler::FATAL_ERROR" (code 2)
Allowed memory size of 134217728 bytes exhausted (tried to allocate 786432 bytes)

is anyway still there & no remedy did work for it !!!

[qualiteam]

Originally Posted by chamitrail@gmail.com

Allowed memory size of 134217728 bytes exhausted (tried to allocate 786432 bytes)

Your memory_limit is set to 128MB. Your server is likely 64-bit, so you should increase it up to 256MB, at least.
Please check this page:
http://kb.x-cart.com/en/general_setup/installation_guide.html#server-requirements

-----

Also, you should restart the web server after editing php.ini, otherwise the changes won't take effect.

[cflsystems]

This is happening on my test installation all the time. After installing a module, after cache regeneration, after not being to store front for days and then try to load it... It goes away on screen refresh but then eventually happens again. It has something to do with Less.php class.
QT has been looking at the issue for a while now - few months - and nothing yet. It was happening on 5.2.x and now same is on 5.3.x.
It doesn't really matter how much memory you allocate to PHP - I have 256 but tried with even 500 - it always reports same numbers for the "out of memory error".

"Out of memory (allocated 133955584) (tried to allocate 1966080 bytes)"

So this is definitely an XC issue. Whether is due to some specific server settings or not I don't know.

[qualiteam]

@chamitrail:
Did restarting the web server help?

@Steve:
I see number of "out of memory" tickets at http://bt.x-cart.com/, but all of them were solved by increasing the memory limit up to 256MB. Also, there are a few tickets with bugs causing the error, but as far as I see all these bugs are fixed by now.