Home > concrete5 for advanced users > if concrete5 causes core dump files

if concrete5 causes core dump files

Recently I noticed that sometimes concrete5 can cause core dump files generated in root concrete5 directory. The files look like core.12345 where 12345 is a process id. It seems that the problem is caused by the application getting out of memory.

You can try to resolve it by increasing memory limit for php. For example, hostgator hosting allows you to upload php.ini file with configuration directives.

You can use the following line to set memory limit to 32 megabytes (or more if you like):

memory_limit = 32M

core dump files contain the application state data only and can be safely deleted without breaking your application. If you are experienced developer or advanced unix user, you can investigate why the application had crashed with gdb utility (GNU project debugger). Use man gdb for reference on the utility usage.

For example:

gdb -c core.4010

It shows the following result:
Core was generated by `/usr/bin/php /home/user/public_html/index.php'.
Program terminated with signal 11, Segmentation fault.
[New process 4010]
#0 0x0830f8bf in ?? ()

Segmentation fault occurs when applications try to access more memory than it is allowed. So try increasing memory limit. That should help you.

Categories: concrete5 for advanced users Tags: