Hi,
I'm running etomite for a hospital intranet and it's working great. Unfortunatley, in the manager section, I get the following error in each of the frames (may have different number of bytes).
[indent]Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 528738736 bytes) in Unknown on line 0[/indent]
Is there a reason there is so much memory being called?
thanks.
Fatal error: allowed memory size - in all frames of manager
Started by Herb, Apr 16 2010 01:55 PM
3 replies to this topic
#1
Posted 16 April 2010 - 01:55 PM
#2
Posted 16 April 2010 - 09:01 PM
Thats a huge amount of memory. Is the site very, very large?
Paul
PS Amazingly I was tinkering with my own site when I discovered the same error although on my live site not in the manager.
Fatal error: Allowed memory size of 8388608 bytes exhausted (tried to allocate 32 bytes) in /public_html/index.php on line 86
When I looked into it I discovered (I think) what has happened. I deleted a folder in the manager and all the children were deleted as well (at least crossed through as if deleted). When I purged the documents though, only the parent folder was deleted, everything else is still in the database. There is no trace of the pages in the manager, but one of my snippets traced pages parents, and with a non existent parent, I think that caused the crash. When I deleted the pages manually from the database, the error dissappeared.
Perhaps this could be a clue to your problem too? Could undeleted orphaned pages in your database be causing the problem? Hope that helps.
(What a coincedence though)
Paul
PS Amazingly I was tinkering with my own site when I discovered the same error although on my live site not in the manager.
Fatal error: Allowed memory size of 8388608 bytes exhausted (tried to allocate 32 bytes) in /public_html/index.php on line 86
When I looked into it I discovered (I think) what has happened. I deleted a folder in the manager and all the children were deleted as well (at least crossed through as if deleted). When I purged the documents though, only the parent folder was deleted, everything else is still in the database. There is no trace of the pages in the manager, but one of my snippets traced pages parents, and with a non existent parent, I think that caused the crash. When I deleted the pages manually from the database, the error dissappeared.
Perhaps this could be a clue to your problem too? Could undeleted orphaned pages in your database be causing the problem? Hope that helps.
(What a coincedence though)
Edited by PaulD, 16 April 2010 - 10:32 PM.
#3
Posted 07 May 2010 - 11:45 PM
The site is not that large. Anyone have any other ideas?
thanks.
thanks.
#4
Posted 08 May 2010 - 11:11 AM
Herb, on 07 May 2010 - 11:45 PM, said:
The site is not that large. Anyone have any other ideas?
thanks.
thanks.
I presume you have checked to see if any snippets are locating orphaned pages and then trying to trace the parent such as in a page trail snippet?
Have any other changes, perhaps by the host, affected anything such as permissions on folders?
If you have a backup, does a reinstall solve it?
Sorry, but no further ideas, sorry.
Paul.
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users











