title: deadlock when using print_r( debug_backtrace( false, 2), true )
body: <p>in reference to this:</p>
  
  <p><a href="https://stackoverflow.com/a/2146171/533426">https://stackoverflow.com/a/2146171/533426</a></p>
  
  <p>the line:</p>
  
  <pre><code>  $trace = print_r( debug_backtrace( false, 2), true );
  </code></pre>
  
  <p>actually deadlocks my php script. That is, the whole application becomes unresponsive, the browser keeps spinning, the debug just jumps into nothing, like, goodbye debug. I can still open the phpmyadmin that runs on the same server, but not the application any longer. The application is actually a slim application that runs in a wordpress installation. Both is unresponsive, no response.</p>
  
  <p>is that eventually because the the variables are too complex to be output?</p>
  
  <p>i have some very complex objects, mainly because i use a plugin that has very complex objects see <a href="http://pods.io/" rel="nofollow noreferrer">pods.io</a> and those <a href="http://pods.io/forums/topic/a-tool-to-output-the-pods-objects-into-the-html/" rel="nofollow noreferrer">pods objects are known to crash things when tried to get output</a> having said that, i think it is quite likely too that slim is causing the crash, because their objects and function call chains are not super short neither.</p>
  
  <p>is there a way to avoid the deadlock?</p>