Fatal error: Allowed memory size of 12582912 bytes exhausted

Next topic

Author	Message
m robo	Sunday 21 January 2007 4:20:48 pm Fatal error: Allowed memory size of 12582912 bytes exhausted (tried to allocate 737280 bytes) in /home/free/tym.sk/a/aait/root/www/share/db_schema.dba on line 6405 Fatal error: eZ publish did not finish its request The execution of eZ publish was abruptly ended, the debug output is present below. get this error after install can anybody help me
kracker (the)	Sunday 21 January 2007 6:03:41 pm Greetings! I would recommend increasing the PHP memory limit. From: <i>http://ez.no/doc/ez_publish/technical_manual/3_8/installation/normal_installation/requirements_for_doing_a_normal_installation#eztoc23485_2_1</i> <i>PHP memory limit issue eZ publish needs at least 64 MB in order to complete the setup wizard. This means that you'll have to increase the default "memory_limit" setting which is located in the "php.ini" configuration file. (Don't forget to restart apache after editing "php.ini".) Normal operation requires about 16 MB. However, it is highly recommended that you keep the 64 MB setting since eZ publish consumes a lot more memory as soon as you use PDF export feature, reindex the search, etc. Multi-lingual sites that store the content in Unicode (UTF-8) will also require at least 64 MB.</i> Related threads, <i>http://ez.no/community/forum/install_configuration/hitting_memory_limit_with_64_mb http://ez.no/content/advancedsearch?SearchText=Allowed+memory+size+&SubTreeArray[]=308&SearchPageLimit=5</i> <i>//kracker titanic - Titanic tehcno remix</i> Member since: 2001.07.13 \|\| http://ezpedia.se7enx.com/
Luke Barton	Monday 22 January 2007 6:30:54 pm m robo, Another approach is this. Set your DebugOutput setting to enabled. If you see several permissions error (e.g., EZP cannot write to error logs, cache files in the var directory, etc.), then you may want to change the permissions, owner and/or group of the var directory until the errors go away. To test, chmod everything with 0777, then tighten things up as much as you can. Good luck. -Luke

Author

Message

Sunday 21 January 2007 4:20:48 pm

Fatal error: Allowed memory size of 12582912 bytes exhausted (tried to allocate 737280 bytes) in /home/free/tym.sk/a/aait/root/www/share/db_schema.dba on line 6405
Fatal error: eZ publish did not finish its request

The execution of eZ publish was abruptly ended, the debug output is present below.

get this error after install can anybody help me

kracker (the)

Sunday 21 January 2007 6:03:41 pm

Greetings!

I would recommend increasing the PHP memory limit.

From: http://ez.no/doc/ez_publish/technical_manual/3_8/installation/normal_installation/requirements_for_doing_a_normal_installation#eztoc23485_2_1

PHP memory limit issue

eZ publish needs at least 64 MB in order to complete the setup wizard. This means that you'll have to increase the default "memory_limit" setting which is located in the "php.ini" configuration file. (Don't forget to restart apache after editing "php.ini".) Normal operation requires about 16 MB. However, it is highly recommended that you keep the 64 MB setting since eZ publish consumes a lot more memory as soon as you use PDF export feature, reindex the search, etc. Multi-lingual sites that store the content in Unicode (UTF-8) will also require at least 64 MB.

Related threads,
http://ez.no/community/forum/install_configuration/hitting_memory_limit_with_64_mb
http://ez.no/content/advancedsearch?SearchText=Allowed+memory+size+&SubTreeArray[]=308&SearchPageLimit=5

//kracker

titanic - Titanic tehcno remix

Member since: 2001.07.13 || http://ezpedia.se7enx.com/

Luke Barton

Monday 22 January 2007 6:30:54 pm

m robo,

Another approach is this. Set your DebugOutput setting to enabled. If you see several permissions error (e.g., EZP cannot write to error logs, cache files in the var directory, etc.), then you may want to change the permissions, owner and/or group of the var directory until the errors go away. To test, chmod everything with 0777, then tighten things up as much as you can.

Good luck.

-Luke

eZ debug

Timing:	Jan 31 2025 01:29:52
Script start
Timing:	Jan 31 2025 01:29:52
Module start 'layout'
Timing:	Jan 31 2025 01:29:52
Module start 'content'
Timing:	Jan 31 2025 01:29:52
Module end 'content'
Timing:	Jan 31 2025 01:29:52
Script end

Main resources:

Total runtime	0.0256 sec
Peak memory usage	6,144.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0057	588.6172	151.2734
Module start 'layout'	0.0057	0.0040	739.8906	220.7656
Module start 'content'	0.0097	0.0143	960.6563	997.8984
Module end 'content'	0.0240	0.0016	1,958.5547	33.9922
Script end	0.0256		1,992.5469

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0028	10.9978	14	0.0002
Check MTime	0.0012	4.6652	14	0.0001
Mysql Total
Database connection	0.0007	2.7471	1	0.0007
Mysqli_queries	0.0027	10.4407	3	0.0009
Looping result	0.0000	0.0550	1	0.0000
Template Total	0.0011	4.5	1	0.0011
Template load	0.0009	3.4700	1	0.0009
Template processing	0.0003	0.9893	1	0.0003
Override
Cache load	0.0006	2.3913	1	0.0006
General
dbfile	0.0013	4.8980	8	0.0002
String conversion	0.0000	0.0261	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded	Edit	Override
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 1 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs