When enabled after switched on of any module display empty page (/admin/modules/list/confirm at the addres bar).
I several times switched on and off the module, but always after switching on blank page is displayed.
When the module is enabled, I turned on another module, but also displays a blank page and translations are not start downloading(Localization update is enabled).
Then I turned off the Diff module, and after that other modules are switched on without problems

Comments

alan d.’s picture

alan d. commented
Component: User interface » Code
Status: Active » Postponed (maintainer needs more info)

Really need more info than just this. Can you turn on PHP error reporting and retry.

Thanks

SimonLitt’s picture

SimonLitt commented

The are no PHP errors in the site log. It seems this error depends on the server configuration. I backup DB and files and deployed on a local server, after that the module is turned on correctly.

And I found following error on the web server:

[Sun Jan 06 10:06:42 2013] [warn] [client 178.127.4.78] mod_fcgid: stderr: PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 1469603 bytes) in /var/www/user2589/data/www/dobronravie.ru/includes/database/database.inc on line 2139, referer: http://dobronravie.ru/admin/modules
alan d.’s picture

alan d. commented
Title: When enabled after switched on of any module display empty page » WSOD when enabled, possible memory issue.
Version: 7.x-3.2 » 7.x-3.x-dev
Priority: Major » Normal
Status: Postponed (maintainer needs more info) » Active

Memory issues are often seen as WSOD. I haven't detected significant overheads in memory usage before, but I will leave this open to investigate more latter.

Diff is a moderate sized module, c/f Smart Trim (small) or Views (large), so I am guessing that this is simply related to the site nearing the memory limit and thus crashing :(

alan d.’s picture

alan d. commented
Status: Active » Closed (cannot reproduce)

Completely un-scientific testing; enabled Devel, note memory usage before and after enabling Diff.

Prior to diff

Memory used at: devel_boot()=1.22 MB, devel_shutdown()=10.86 MB, PHP peak=11.75 MB.
Memory used at: devel_boot()=1.58 MB, devel_shutdown()=10.86 MB, PHP peak=11.75 MB.

After diff

Memory used at: devel_boot()=1.58 MB, devel_shutdown()=10.92 MB, PHP peak=11.5 MB.
Memory used at: devel_boot()=1.58 MB, devel_shutdown()=10.92 MB, PHP peak=11.5 MB.

From these results, it does not appear to warrant any further testing. This is backed by the fact that this is the first time that this has been reported (9,243 users of 7.x-3.2). This was simply the straw that broke the camels back when it came to memory limits on your site afaict.

One thing that is common on all of our bigger sites is that database logging often sucks memory. Try to resolve anything getting logged here. And apart from that, if you can not increase the already high memory limit, is to remove unused modules, etc. Good luck with things

alan d.’s picture

alan d. commented
Issue summary: View changes

Сorrect inaccurate