Hello,

after my site was working a few months without errors, I can not get into the admin/pages panel. The loader is spinning until an error message like "Fatal error: Allowed memory size of 125829120 bytes exhausted (tried to allocate 614 bytes) in (...)/framework/model/Database.php on line 772" becomes visible.

I did some research on memory, did a phpinfo() inside the SilverStripe folder which gives 120M as memory limit. It is a small site and the dimensions of 120M are just absurd.

I have some other DataObjects like admin/MYDATAOBJECT which _do_ work via direct linking in the address bar.

However, admin/pages, admin/assets, do not work. It seems like all the standard pages in the admin backend do not load.

Frontend does work properly.

admin/settings: working
admin/pages: not working
admin/assets: not working
admin/security: working
admin/reports: working
admin/OWNDATAOBJECTS: All working!

What could be the error? How to debug?

Thank you!

Sorry for the late reply, hope you found your solution already. Just in case:

Many times these memory exhaustion issues are not the result of actually having too little memory available, but of some sort of error, possibly php getting into a loop, requesting ever more memory until it dies.

I sometimes saw this was where a client had rearranged or changed the pagetype of one or more existing pages in the CMS and something went wrong, after which they could no longer enter the CMS. This had to be fixed in the database. Do you remember the last page you changed/added? You could start by checking your SiteTree tables for a missing ClassName. Or even possibly PageID's pointing to eachother in a circular fashion (had that happen too).

To debug: at least be sure to place your website into dev mode, read more here http://doc.silverstripe.org/framework/en/topics/debugging.

If you absolutelydidn't change anything yourself, could it be that your provider changed something? I had a simular problem where a provider upgraded from php 5.3 to 5.4 without my knowledge (renewing the silverstripe-cache fixed that), but that affected the frontend as well.

Another quick tip is to ensure you are freeing memory - for a discussion on that see - http://www.silverstripe.org/general-questions/show/16988