Just after the installation of all the modules, the bar gets to 100% (the last one is Commons) and then as it's flipping to the next step, I'm getting a WSOD.

Here's the output from php_error.log:

[19-Dec-2012 13:20:24] PHP Fatal error:  Allowed memory size of 134217728 bytes exhausted (tried to allocate 87 bytes) in /Users/abyron/Sites/commons/site/includes/menu.inc on line 3731
19-Dec-2012 13:20:24] PHP Stack trace:
[19-Dec-2012 13:20:24] PHP   1. {main}() /Users/abyron/Sites/commons/site/install.php:0
[19-Dec-2012 13:20:24] PHP   2. install_drupal() /Users/abyron/Sites/commons/site/install.php:26
[19-Dec-2012 13:20:24] PHP   3. install_run_tasks() /Users/abyron/Sites/commons/site/includes/install.core.inc:77
[19-Dec-2012 13:20:24] PHP   4. install_run_task() /Users/abyron/Sites/commons/site/includes/install.core.inc:339
[19-Dec-2012 13:20:24] PHP   5. _batch_page() /Users/abyron/Sites/commons/site/includes/install.core.inc:449
[19-Dec-2012 13:20:24] PHP   6. _batch_finished() /Users/abyron/Sites/commons/site/includes/batch.inc:89
[19-Dec-2012 13:20:24] PHP   7. _install_profile_modules_finished() /Users/abyron/Sites/commons/site/includes/batch.inc:466
[19-Dec-2012 13:20:24] PHP   8. drupal_flush_all_caches() /Users/abyron/Sites/commons/site/includes/install.core.inc:1559
[19-Dec-2012 13:20:24] PHP   9. module_invoke_all() /Users/abyron/Sites/commons/site/includes/common.inc:7393
[19-Dec-2012 13:20:24] PHP  10. call_user_func_array() /Users/abyron/Sites/commons/site/includes/module.inc:857
[19-Dec-2012 13:20:24] PHP  11. features_flush_caches() /Users/abyron/Sites/commons/site/includes/module.inc:0
[19-Dec-2012 13:20:24] PHP  12. features_rebuild() /Users/abyron/Sites/commons/site/profiles/commons/modules/contrib/features/features.module:239
[19-Dec-2012 13:20:24] PHP  13. _features_restore() /Users/abyron/Sites/commons/site/profiles/commons/modules/contrib/features/features.module:915
[19-Dec-2012 13:20:24] PHP  14. features_invoke() /Users/abyron/Sites/commons/site/profiles/commons/modules/contrib/features/features.module:889
[19-Dec-2012 13:20:24] PHP  15. call_user_func_array() /Users/abyron/Sites/commons/site/profiles/commons/modules/contrib/features/features.module:534
[19-Dec-2012 13:20:24] PHP  16. field_instance_features_rebuild() /Users/abyron/Sites/commons/site/profiles/commons/modules/contrib/features/features.module:0
[19-Dec-2012 13:20:24] PHP  17. field_create_instance() /Users/abyron/Sites/commons/site/profiles/commons/modules/contrib/features/includes/features.field.inc:274
[19-Dec-2012 13:20:24] PHP  18. module_invoke_all() /Users/abyron/Sites/commons/site/modules/field/field.crud.inc:499
[19-Dec-2012 13:20:24] PHP  19. call_user_func_array() /Users/abyron/Sites/commons/site/includes/module.inc:857
[19-Dec-2012 13:20:24] PHP  20. registration_field_create_instance() /Users/abyron/Sites/commons/site/includes/module.inc:0
[19-Dec-2012 13:20:24] PHP  21. _registration_menu_rebuild() /Users/abyron/Sites/commons/site/profiles/commons/modules/contrib/registration/includes/registration.field.inc:314
[19-Dec-2012 13:20:24] PHP  22. menu_rebuild() /Users/abyron/Sites/commons/site/profiles/commons/modules/contrib/registration/includes/registration.field.inc:336
[19-Dec-2012 13:20:24] PHP  23. menu_router_build() /Users/abyron/Sites/commons/site/includes/menu.inc:2712
[19-Dec-2012 13:20:24] PHP  24. _menu_router_build() /Users/abyron/Sites/commons/site/includes/menu.inc:2753

Comments

ezra-g’s picture

ezra-g commented

From the stack trace, this appears to be related to


/*
 * Revert Features after the installation.
 */
function commons_revert_features() {
  // These features must be twice in a row in order to
  // fully revert.
  $i = 0;
  while ($i < 2 ) {
   // Revert Features components to ensure that they are in their default states.
    $revert = array(
      'commons_groups' => array('field_instance'),
      'commons_wikis' => array('og_features_permission'),
    );
    features_revert($revert);
    $i++;
  }
}

We should no longer need to do this twice following http://drupal.org/node/1782922#comment-6752174 .

jpontani reported exhausting the memory limit doing a feature export post-installation.

ezra-g’s picture

ezra-g commented
Status: Active » Fixed

This block of code was refactored with http://drupal.org/node/1866832#comment-6865832. Please re-open if you experience this problem again. Thanks!

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

japerry’s picture

japerry
Location KOMK
commented
Status: Closed (fixed) » Active

It looks like the installer requires 196M and 60seconds for execution. I've setup the installer to set the ini to these limits on install for it doesn't WSOD anymore.

japerry’s picture

japerry
Location KOMK
commented
Status: Active » Fixed

Fix is committed here:

http://drupalcode.org/project/commons.git/blobdiff/074baab1402be481ea4fb...

dehacker’s picture

dehacker commented

Fresh install of beta2 on VBox Ubuntu with Quickstart profile I receive the following error :

Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 122880 bytes) in /home/quickstart/websites/issue.dev/profiles/commons/modules/contrib/ctools/plugins/content_types/node_context/node_terms.inc on line 106 Call Stack: 0.0001 644600 1.

defaults:
max_input_time = 60
memory_limit = 128M

Resetting memory_limit to 256M in settings.php completes the installation.

blacklabel_tom’s picture

blacklabel_tom commented

Same issue here on quickstart, I haven't had a problem installing outside of quickstart

matt v.’s picture

matt v. commented

On a related note, in the last day or two I had to up the max_execution_time when using drush site-install. I haven't taken the time to pinpoint the precise requirement; I just upped it from 60 to 180.

socialnicheguru’s picture

socialnicheguru commented

this caused errors because it was not enough time

In the Readme maybe you could say add the following to the settings.php file and increase the number of seconds.
ini_set('max_execution_time', '120');

this overwrote my settings in php5/apache2/php.ini and php5/cli/php.ini
ini_set('max_execution_time', '60');

It would have been nice to know it was set somewhere

japerry’s picture

japerry
Location KOMK
commented

Is everyone who is testing using the dev install, or beta2? Beta2 does not set a memory or execution limit on the installer, while the latest dev snapshot (Feb 8th) does. Judging by the "134217728 bytes exhausted" error, it looks like you do not have the most recent version.

The info file is going to require a minimum of 128m and 60 seconds execution time to operate. There are issues with upping the default memory limits globally, because for many hosts this will take down the maximum amount of php processes. (IE you have 2GB max memory = 16/128m php processes, or 8/256m php processes)

Therefore the aim for commons, in general, is to never need to take over 128m in a single operation. However, there are installation tasks that do require above 128m, hence why we make a temporary override during the install process to 196m. Once commons is installed, you can verify that the memory limit is set to your php.ini by checking the php status under site status.

blacklabel_tom’s picture

blacklabel_tom commented

I was using beta2

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.