search

umanda / dompdf

exported from code.google.com/p/dompdf.
0 stars 0 forks source link

Maximum function nesting level thrown by debugger #450

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?

Three SPAN elements inside a DIV element, followed by the same. (see samples) 
Configured to enable FLOAT, get the error. No error if FLOAT is disabled, but 
it renders incorrectly.

What is the expected output? What do you see instead?

Expected a nice rendered "THIS.....THAT" format. Instead got:

Fatal error: Maximum function nesting level of '100' reached, aborting! in 
dompdf\include\style.cls.php on line 1128

What version of dompdf are you using? What version of PHP? On what
operating system?

dompdf-0-6-0-b3, php 5.2

Please provide the HTML source code you want to convert, or any additional 
information.

This is a small, uncomplicated, html file, with a small css file. This snipet 
renders fine in chrome or firefox.

Original issue reported on code.google.com by LRH...@gmail.com on 23 Mar 2012 at 2:14

Attachments:

GoogleCodeExporter commented 8 years ago 
I'm getting the same issue php 5.3.1

Original comment by PerryGov...@gmail.com on 30 Apr 2012 at 6:15

GoogleCodeExporter commented 8 years ago 
Based on what I'm seeing with a quick web search this error is due to limits 
implemented by a debugger (e.g. xDebug, Zend). You should either disable your 
debugger or increase the recursion limit. I'm not sure what would be an 
appropriate limit for DOMPDF.
http://www.google.com/search?q=php+maximum+nesting+level

I'm keeping this issue alive, however, because it could point to an area that 
could affect performance. A lot of work has been done to improve performance, 
but there is still a significant amount of recursion due mainly to the nature 
of processing the DOM and handling style cascade.

Original comment by eclecticgeek on 13 May 2012 at 2:40

GoogleCodeExporter commented 8 years ago 
Issue 480 has been merged into this issue.

Original comment by eclecticgeek on 13 May 2012 at 3:37

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
This may be a problem with the CSS float, I noticed something like this, but 
without any debugger.

Original comment by fabien.menager on 8 Aug 2012 at 1:07

GoogleCodeExporter commented 8 years ago

Original comment by eclecticgeek on 24 May 2013 at 3:00