"Fatal error: Maximum execution time of 30 seconds exceeded in /includes/file.inc on line 927." It seems that the drupal_system_listing() call, which calls file_scan_directory(), which is slow. If this is unavoidable, can we call set_time_limit(0) if not in safe mode?

Comments

sun’s picture

sun
Primary language German
Location Karlsruhe
commented
Priority: Normal » Critical

Me too. Tried to enable all core modules and few contrib modules at one fell swoop in latest Drupal 6.x.

mot’s picture

mot commented

Can anyone confirm this for 7.x please?

cwgordon7’s picture

cwgordon7 commented

Yes. The original report was for 7.x. Though perhaps this should be fixed in 6.x too (perhaps not).

mot’s picture

mot commented

30 seconds for a php script is quite a long time.

What steps are needed to reproduce the problem?

Additional Questions:
* What does this function do?
* Is this related to the number of modules installed?
* Is this a one-time task? Is this an installation task?

Some more data and infos would help me to dig more into this. I can check against 6.5.

Anonymous’s picture

Anonymous (not verified) commented
Status: Active » Postponed (maintainer needs more info)

bumping status.

cwgordon7’s picture

cwgordon7 commented

What steps are needed to reproduce the problem?

Be on a moderately slow machine.

What does this function do?

http://api.drupal.org/api/function/file_scan_directory/7 and http://api.drupal.org/api/function/drupal_system_listing/7, depending on which function you're asking about.

Is this related to the number of modules installed?

This should not be related to the number of modules installed, since modules are installed through the batch api, and it is only the system listing that is too slow.

Is this a one-time task? Is this an installation task?

This is on installation of Drupal core with the default profile.

Some additional system information about my particular environment:
Windows XP
Apache 2.2.8
MySQL 5.0.51b
PHP 5.2.6

sun.core’s picture

sun.core commented
Status: Postponed (maintainer needs more info) » Closed (won't fix)

Sorry, without further information this issue can only be marked as won't fix.

Feel free to re-open this issue if you want to provide further information. Thanks.