After rebuilding my system using 4.5.0, admin/modules seems to crash when certain modules are included in the modules directory. Including a custom module that I built for my system. If I remove the problem module from the directory admin modules works fine and displays a list of the modules. However with it in place, the command seems to crash resulting in a "page cant be displayed" error to be shown in the browser. Similiar issues exist with other 4.5.0 released modules from the download page including the filemanager module. No errors are being logged to the webserver log. So I'm stumped as to where to look for the failure source. Any ideas?

Comments

killes@www.drop.org’s picture

Category: bug » support
Priority: Critical » Normal

Can you describe the crash with some more words? What is in your log files? I think your module must be doing something nasty. it is certainly not an admin.module bug.

NaSPA1’s picture

That's just what's stumping me about this problem. The Apache's error_log is empty - no signs of a problem occurring in the module. The references aren't appearing in access_log either. Do you have any suggestions for other places to look?

Radi

killes@www.drop.org’s picture

I suspect that you hit a memory limit. Drupal includes all modules on that page. This might to lead to a request for more momory than allowed for php. Try removing some modules.

NaSPA1’s picture

Thanks it definitely seems I am on the cusp of the memory limit. I've remove just about every extraneous module I installed to 'try' and the problem has been alleviated somewhat. Guess I need to see about cranking up the amount of available memory.

killes@www.drop.org’s picture

Ok, marking fixed.

Anonymous’s picture

mdowsett’s picture

How can you adjust the amount of available memory? My site is on an ISPs server so I don't have as much freedom as I may need. I am running into this same issue.

avpaderno’s picture

Version: » 7.x-dev
Component: admin.module » other