Closed (won't fix)
Project:
Drupalgeddon
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
17 Nov 2014 at 17:21 UTC
Updated:
6 Jan 2015 at 03:17 UTC
Jump to comment: Most recent
Comments
Comment #1
SpenserJ commentedIncreasing the memory of a specific Drupal site will not have an effect, as Drush runs via PHP-CLI. Type
php -i | grep 'memory_limit'and see if that is showing the same memory limit that you expect.Chances are that the memory limit is not the core issue though. My first guess would be that you have a large number of files/folders, and it is trying to check each of them. I'm not sure if there is much advice I could give you without knowing what files/folders are in your Drupal install.
Comment #2
xurizaemonComment #3
radiobuzzer commentedYes, the website is pretty big and there is a big amount of files and modules:
all/modules: 208 modules
sites: 9 sites
sites/mysite.com/files: 1008 files
sites/mysite2.com/files: 38 files (script crashes on both sites)
The question is, if this is the problem, how can it be fixed.
The module is not mentioning any limit on the amount of modules or files.
So if it raises memory issues, this should indeed be a bug.
Comment #4
radiobuzzer commentedComment #5
xurizaemon@radiobuzzer your contributions to debugging and improving tools on Drupal.org are most welcome.
To help resolve this, you could -
Contributions on Drupal.org are offered freely, but there is no guarantee or implicit support with that - just a community. You may need to be the one to scratch your own itch here. Opening an issue is a great start because it can connect you with other engaged folk in the same boat.
If you're the only one seeing this bug, you need to be the one to decide what to do next.
HTH
Comment #6
xurizaemonClosing due to lack of response from reporter.