2

This question already has an answer here:

I have a problem after importing the PO of the Drupal core 7.28 (I tried with French and Arabic), whenever I try to create a new feature or open the modules page, I will get an error:

Allowed memory size of 268435456 bytes exhausted (tried to allocate 5126472 bytes) in .../includes/form.inc on line 3906

After the import, it is consuming a lot of memory and time I tried debugging, this is the path I could trace:

menu_execute_active_handler -> drupal_get_form -> drupal_build_form -> features_export_form -> _features_export_form_components -> _features_export_build

This is as far as I could get while debugging. The last function _features_export_build takes a lot of time but I couldn’t know what is wrong inside.

marked as duplicate by kenorb, Adrian Cid Almaguer, No Sssweat, Krishna Mohan, Scott Joudry Mar 21 '16 at 16:36

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

  • Do you use features_translations module? – FriOne Jul 29 '14 at 12:18
  • yes I do but this happens even before integrating anything with features – beginner1 Jul 30 '14 at 13:27
  • Not use it, it not working with many tranlsation strings. Better import translations throw 'po' files. – FriOne Jul 30 '14 at 15:37
  • But now error exists because of features, yes?* – FriOne Jul 30 '14 at 15:41
  • but how can I automatically integrate the po on install? – beginner1 Jul 31 '14 at 9:08
0

Generating/exporting Feature modules takes a lot of memory, depending on amount of components which you're trying to export. The Features module is constantly improving, so please check the recent stable version if that makes the difference.

Otherwise you've to increase your PHP memory limit either in your php.ini or before the import, temporary add this line into your settings.php file:

ini_set('memory_limit','1G');

If you would like to debug what takes so much memory, then you need to use PHP profiler such as XDebug (xdebug.profiler_enable=1) or use XHProf.

Not the answer you're looking for? Browse other questions tagged or ask your own question.