This is related to the latest committed code in
#2123315: Pager does not appear if fields use Views PHP (7.x-1.x)
and
#2614186: PHP fatal error
The views_php_views_post_build() is causing some views to consume huge memory. Increased to 1G memory_limit also not enough. Commented out the code solves the issue.
Example views having issue, node administration from admin_views with over 1M content. Even filter to content type with 300K content also having the same issue.
Errors:
FastCGI: server "/usr/lib/cgi-bin/php5-fcgi" stderr: PHP message: PHP Warning: Unknown: Input variables exceeded 1000. To increase the limit change max_input_vars in php.ini. in Unknown on line 0, referer: http://drupalsite.local/admin/content
FastCGI: server "/usr/lib/cgi-bin/php5-fcgi" stderr: PHP message: PHP Fatal error: Allowed memory size of 377487360 bytes exhausted (tried to allocate 48 bytes) in /var/drupal/sites/all/modules/contrib/views/plugins/views_plugin_query_default.inc on line 1491, referer: http://drupalsite.local/admin/content
Content of $view->build_info: http://pastebin.com/Gbbimq64
Comments
Comment #2
ckng- deleted -
Comment #3
ckngComment #4
ckngEncounter this again when a custom views is added under /admin/* path.
The views query limit is removed by
views_php_views_post_build()causing rows to be loaded, which explain the overflow in the original issue with admin_views.Here is $view->build_info['query'] dump
Comment #5
skylord commentedSeems like duplicate of #2628014: Pager fix causes performance and memory regression - please, try patch from #2628014-4: Pager fix causes performance and memory regression
Comment #6
mustanggb commented