Fatal error: Maximum function nesting level of '100' reached, aborting! in /Users/robert/Sites/d7/includes/bootstrap.inc on line 1162

This when using the search form from the search block. The search form on q=search works fine.

Comments

robertdouglass’s picture

Note: I don't claim to know for sure that the registry patch caused this but it is the biggest change to the codebase that happened recently. Not to lead anyone down false alleyways =)

catch’s picture

enabled all core modules and can't reproduce this - anything specific you were doing?

robertdouglass’s picture

Project: Drupal core » Devel
Version: 7.x-dev » 7.x-1.x-dev
Component: base system » devel
Priority: Critical » Normal

Indeed. The bug is dependent on devel module being enabled and the "Display redirection page" option checked. Moving to be a devel module bug.

robertdouglass’s picture

Title: Registry: Maximum function nesting level of '100' reached, aborting! » Devel + search block: Maximum function nesting level of '100' reached, aborting!
chx’s picture

Given the patch you filed at the registry issue, you aure listed the files devel has in .info as the upgrade docs say?

dman’s picture

Although I do have devel on, that option was not checked, and I maxed out at
Fatal error: Maximum function nesting level of '50' reached, aborting!
It seems it's not devel so much as an xdebug setting. On my setup anyway.
I went looking at my /etc/php5/apache2/conf.d/xdebug.ini and bumped it up to:

xdebug.max_nesting_level = 150

My copy&paste install of xdebug had it at 50.

FWIW, the job I was doing to get the trace was certainly not to onerous (no recursive loops) and came down to:
- 9 steps from execute_active_handler() to the end of my form submission (which actually didn't validate and wanted to return a message)
- 10-37 were all recursive theme loops trying to build the current menu context. Just 4 levels deep, but heaps of theme fallbacks!
- 38-50 was just attempting to create a link on the 4th menu leaf!
- - theme_menu_item() .. theme_menu_item_link() ... l() ... drupal_get_path_alias() ... db_escape_string() - Death.

Good grief! :-}

moshe weitzman’s picture

Status: Active » Postponed (maintainer needs more info)

Someone has to dig down and find the root cause and solution.

Anonymous’s picture

Hi i installed the devel module and i added test data. I then tried to delete the test data and got Maximum function nesting level of '100' reached,. I uninstalled the model but still had the same problem. How I seemed to fix it was too clear my cache and fingers crossed the error hasnt occured again. I will keep monitoring the situation. I think there are some stability issues with the devel module. I am wondering from a earlier post by dman

dman’s picture

I can't say that there is a root cause, it seems that the entire architecture is quite able to dig a hole a hundred function-calls deep just by doing what it's told.
As above, I hit over 50 levels of nesting rendering a 4-level menu (traced in xdebug).

To find what's triggering this 100-level hole, you'd be best to try xdebug also for some clues.

willzyx’s picture

Issue summary: View changes
Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)

Closing for lack of activity. Feel free to reopen if the issue still exists