Solution for Fatal error Maximum function nesting level of 100 reached aborting in PHP

Question

I have made a function that finds all the URLs within an html file and repeats the same process for each html content linked to the discovered URLs  The function is recursive and can go on endlessly  However  I have put a limit on the recursion by setting a global variable which causes the recursion to stop after 100 recursions  However  php returns this error   Fatal error  Maximum function nesting level of  100  reached  aborting  in D  wamp www crawler1 simplehtmldom 1 5 simple html dom php on line 1355   I found a solution here  Increasing nesting function calls limit but this is not working in my case  I am quoting one of the answers from the link mentioned above  Please do consider it    quot Do you have Zend  IonCube  or xDebug installed  If so  that is probably where you are getting this error from  I ran into this a few years ago  and it ended up being Zend putting that limit there  not PHP  Of course removing it will let  gt you go past the 100 iterations  but you will eventually hit the memory limits  quot   Is there a way to increase the maximum function nesting level in PHP

User · Answer

Another solution is to add xdebug max nesting level   200 in  your php ini

User · Answer

Stumbled upon this bug as well during development  However  in my case it was caused by an underlying loop of functions calling eachother - as a result of continuous iterations during development  For future reference by search engines - the exact error my logs provided me with was  Exception  Maximum function nesting level of  256  reached  aborting   If  like in my case  the given answers do not solve your problem  make sure you re not accidentally doing something along the lines of the following simplified situation  function foo           Do something     bar       function bar           Do something else     foo       In this case  even if you set ini set  xdebug max nesting level   9999   it will still print out the same error message in your logs

User · Answer

It s also possible to fix this directly in php  for example in the config file of your project    ini set  xdebug max nesting level   200

User · Answer

probably happened because of xdebug   Try commenting the following line in your  php ini  and restart your server to reload PHP        xdebug max nesting level

User · Answer

Check recursion from command line   php -r  function foo     static  x   1  echo  foo     x      n   foo      foo       if result   100 THEN check memory limit

User · Answer

A simple solution solved my problem  I just commented this line   zend extension    d  wamp bin php php5 3 8 zend ext php xdebug-2 1 2-5 3-vc9 dll   in my php ini file  This extension was limiting the stack to 100 so I disabled it  The recursive function is now working as anticipated

User · Answer

php ini      xdebug max nesting level   -1   I m not entirely sure if the value will ever overflow and reach -1  but it ll either never reach -1  or it ll set the max nesting level pretty high

User · Answer

Try looking in  etc php5 conf d  to see if there is a file called xdebug ini  max nesting level is 100 by default  If it is not set in that file add   xdebug max nesting level 300   to the end of the list so it looks like this  xdebug remote enable on xdebug remote handler dbgp xdebug remote host localhost xdebug remote port 9000 xdebug profiler enable 0 xdebug profiler enable trigger 1 xdebug profiler output dir  home drupalpro websites logs profiler xdebug max nesting level 300   you can then use  Andrey s test before and after making this change to see if worked   php -r  function foo     static  x   1  echo  foo     x      n   foo      foo

User · Answer

You could convert your recursive code into an iterative code  which simulates the recursion  This means that you have to push the current status  url  document  position in document etc   into an array  when you reach a link  and pop it out of the array  when this link has finished

User · Answer

on Ubuntu using PHP 5 59    got to          etc php5 cli conf d   and find your xdebug ini in that dir  in my case is  20-xdebug ini  and add this line       xdebug max nesting level   200    or this      xdebug max nesting level   -1   set it to -1 and you dont have to worry change the value of the nesting level

User · Answer

In your case it s definitely the crawler instance is having more Xdebug limit to trace error and debug info   But  in other cases also errors like on PHP or core files like CodeIgniter libraries will create such a case and if you even increase the x-debug level setting it would not vanish   So  look into your code carefully       Here was the issue in my case   I had a service class which is library in CodeIgniter  Having a function inside like this    class PaymentService        private  CI       public function   construct               this- gt CI   amp  get instance             public function process         lots of Ci referencing here           My controller as follow    this- gt load- gt library  PaymentService     this- gt process        see I got this wrong instead  it shoud be like    Function call on last line was wrong because of the typo  instead it should have been like below    this- gt Payment service- gt process      the library class name   Then I was keeping getting the exceed error message  But I disabled XDebug but non helped  Any way please check you class name or your code for proper function calling

User · Answer

Rather than going for a recursive function calls  work with a queue model to flatten the structure    queue   array  http   example com first url    while  count  queue          url   array shift  queue         queue   array merge  queue  find urls  url       function find urls  url         urls   array            Some logic filling the variable      return  urls      There are different ways to handle it  You can keep track of more information if you need some insight about the origin or paths traversed  There are also distributed queues that can work off a similar model

User · Answer

Another solution if you are running php script in CLI cmd  The php ini file that needs edit is different in this case  In my WAMP installation the php ini file that is loaded in command line is   wamp bin php php5 5 12 php ini  instead of  wamp bin apache apache2 4 9 bin php ini which loads when php is run from browser

User · Answer

Increase the value of xdebug max nesting level in your php ini

User · Answer

Rather than disabling the xdebug  you can set the higher limit like     xdebug max nesting level 500

User · Answer

You could try to wiggle down the nesting by implementing parallel workers  like in cluster computing  instead of increasing the number of nesting function calls   For example  you define a limited number of slots  eg  100  and monitor the number of  workers  assigned to each some of them  If any slots become free  you put the waiting workers  in them

User · Answer

I had this issue with WordPress on cloud9  It turns out it was the W3 Caching plugin  I disabled the plugin and it worked fine

User · Answer

I had a error when i was installing many plugins So the error 100 showed including the location of the last plugin that i installed C  wamp www mysite wp-content plugins       so i deleted this plugin folder on the C  drive then everything was back to normal I think i have to limit the amount of plug-in i install or have activated   good luck i hope it helps

User · Answer

I had the same problem and I resolved it like this   Open MySQL my ini file In  mysqld  section  add the following line  innodb force recovery   1 Save the file and try starting MySQL Remove that line which you just added and Save

User · Answer

You can also modify the  debug  function in modifier debug print var php  in order to limit its recursion into objects    Around line 45  before     results      lt br gt     str repeat   amp nbsp     depth   2        lt b gt  - amp gt     strtr  curr key    replace      lt  b gt          smarty modifier debug print var  curr val     depth   length     After     max depth   10   results      lt br gt     str repeat   amp nbsp     depth   2        lt b gt  - amp gt     strtr  curr key    replace      lt  b gt            depth  gt   max depth    Max recursion depth       depth    smarty modifier debug print var  curr val     depth   length      This way  Xdebug will still behave normally  limit recursion depth in var dump and so on  As this is a smarty problem  not a Xdebug one

User · Answer

lt  php ini set  xdebug max nesting level   9999       your code       P S  Change 9999 to any number you want

User · Answer

Go into your php ini configuration file and change the following line   xdebug max nesting level 100   to something like   xdebug max nesting level 200

User · Answer

If you re using Laravel  do  composer update   This should be work

[recursion] Solution for "Fatal error: Maximum function nesting level of '100' reached, aborting!" in PHP

Examples related to recursion

Examples related to xdebug

Examples related to php