> drush cc
select 1

I get the following error:

Error: Allowed memory size of 314572800 bytes exhausted (tried to
allocate 79691776 bytes) in
/profiles/openatrium/modules/contrib/features/features.export.inc(574)

this is the line

 $cache[$module_name][$component] = isset($code[$default_hook]) ? eval($\code[$default_hook]) : FALSE;

Is it necessary for features to read in all values for all modules when I am trying to clear all caches?

Comments

socialnicheguru’s picture

socialnicheguru commented

while the memory error goes away if I allocate 400M to accomodate features, is there a way to disable this for drush so that I don't need to allocate so much memory?

socialnicheguru’s picture

socialnicheguru commented
Title: I run out of memory when I run drush cc and select 1. Is it necessary for features to re-initialize cache? » Fatal error. Run out of memory. Poor performance for features module.

I run out of memory when I run drush cc and select 1. Is it necessary for features to re-initialize cache?

cpotter’s picture

cpotter commented

Run out of memory also when doing a basic 'features create', even with 750MB !!!

cpotter’s picture

cpotter commented

In fact it is a problem with the "Elysia Cron" module. If disabled, Features Create works fine.

mpotter’s picture

mpotter commented

@cpotter: great, glad you tracked down the problem on your site. To everybody else in this thread, if you post about having memory problems, you MUST also report what specific Features you are using and what other modules. As #4 shows, it's often a problem with a conflicting module. Sometimes it can be a problem with the specific feature that you have exported. As with all debugging, it's useful to go through your site and disable whatever modules you can to track down which module is causing the problem.

With Features, try disabling your specific Feature exportables to see if you can determine which one is causing the problem. We need to know if it's a Views feature, or a Content Type, or a Field, etc.

I've personally used Features on very large and complex web sites with less than 256MB with no problems. But please post as much information as possible or else your issue will just get closed for "cannot reproduce".

tjmoyer’s picture

tjmoyer commented

cpotter, could you elaborate a bit? We just put Elysia Cron on our dev site and ran into the same problem. Disabling Elysia Cron does solve the problem, but I don't see anything in that module's queue about this issue. Do you know what within Elysia Cron is causing the trouble? Can you elaborate?

tjmoyer’s picture

tjmoyer commented

Now I found the issue in Elysia Cron's queue: http://drupal.org/node/1357836. Looks like the dev version is the way to go until they release a new stable version upgrade.

mpotter’s picture

mpotter commented
Status: Active » Closed (won't fix)

Closing this for lack of activity. Please re-open this issue if you can reproduce it in the latest version.