Got my hosting provider to kindly up my php memory_limit to 128Mb during install of OpenPublic (beta3). Installation went smooth, site looked great. Three days later the memory setting returned to 64Mb. This did not break the site, but did lead to error messages in certain parts of the site. Especially when I try to go into the admin/modules to (de)select things, I get a memory error.

Have since upgraded to OpenPublic beta4, for a little bit all went well, now, whenever I try and run cron, updates.php, or admin/structure/features, I get a memory error in this style:
Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 31457280 bytes) in /home/***/public_html/profiles/openpublic/modules/features/openpublic_demo_content/openpublic_demo_content.features.content.inc on line 19691

So even though apparently only half of the memory allocated is asked for it still hangs..

When I try editing openpublic_demo_content.features.content.inc my editor crashes! And I get error messages referring to the same fatal error related other pages too. Changing theme does not help, any settings changes do not help..

I was wondering if it is known which bits of the OpenPublic install require the 128Mb after install, so I could switch those off?

Help appreciated!

Xander

Comments

xax’s picture

xax
Location London, UK
commented
Version: 7.x-1.0-beta3 » 7.x-1.0-beta4

removed, now in core message

xax’s picture

xax
Location London, UK
commented

removed, now in core message

xax’s picture

xax
Location London, UK
commented
Priority: Normal » Major

Have upgraded to major as it renders my installation unworkable, but I don't know whether others suffer the same fate..

greenerr’s picture

greenerr commented

It's memory heavy - I have my php memory limit set at 220MB for it to work correctly (also what they recommend). With lower limits I ran in to the same issue you are having.

e2thex’s picture

e2thex commented

Open public demo content is a very large feature. It looks like features is rebuilding something on your cache clears. I think turning off this module will most likely help a good amount.

Note if you are doing a new install and your remove it from the dep list in openpublic.info it will not get turned on in the first place. While the site will not look as snazzy, all of the functionality will be present.

xax’s picture

xax
Location London, UK
commented

#4, #5, thanks, yes, I thought that the prefab content might be the culprit. I got around things for now but dumping the database, then do a new install. Instead of choosing the 'Openpublic' install profile I chose standard, after installation I could then switch on most of the other nice modules coming with OpenPublic.

Still hit a few snags when I run cron or update modules, keep getting "Allowed memory size of 67108864 bytes exhausted (tried to allocate 82 bytes)" errors, but just pressing refresh (sometimes more than once), and all settings are executed, cron is run, etc.

Do have to say however that most of the nice features ready to rock in OpenPublic then need to be recreated by hand. No custom page types/views anymore.. Lay-out suddenly meagre.. etc.

agileware’s picture

agileware commented
Version: 7.x-1.0-beta4 » 7.x-1.0-beta8

Disabled the openpublic_pages module in the openpublic.info file. This was causing PHP Fatal error during Drush installations.

PHP Fatal error: Allowed memory size of XXX bytes exhausted (tried to allocate YYY bytes) openpublic/modules/contrib/features/features.export.inc on line 536

agileware’s picture

agileware commented
Issue summary: View changes

rewrote message to incorporate my own comments, and reflect the upgrade I did from beta3 to beta4

hefox’s picture

hefox commented
Issue summary: View changes
Status: Active » Closed (won't fix)

Sorry but sounds like need higher limit