Very common problem. The admin/modules page has to parse the code for *all* modules on the site, whether enabled or not. Once you start adding a lot of modules beyond the core set, that can get big, fast, and break the 8 MB memory limit on PHP that is the typical default. You'll need to increase the memory size. I suggest 24 MB to give yourself room to grow. (I've yet to hit that limit personally.)
There are a couple of plans to help reduce memory usage in future versions of Drupal, but for now 4.6 and 4.7 both have this issue.
On Sunday 29 January 2006 19:02, Jiann-Ming Su wrote:
I've been working on a site today. Everything seems to be going well. But, all of a sudden, when I try to Administer->Modules, the page comes back blank. I was installing, enabling, and disabling modules just earlier without problems. Now, I just get a blank page for http://my_drupal_site/admin/modules. All the other administrative links seem to work. I did find the following in the httpd error_log:
Allowed memory size of 8388608 bytes exhausted (tried to allocate 64 bytes)
What did I do wrong?
-- Jiann-Ming Su "I have to decide between two equally frightening options. If I wanted to do that, I'd vote." --Duckman "The system's broke, Hank. The election baby has peed in the bath water. You got to throw 'em both out." --Dale Gribble