search

sivasekar / dompdf

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

Possible infinite loop #34

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Create an HTML document that uses inline-table styling on an element
contained within another element (i.e. div within a div).
2. Attempt to render the document.

What is the expected output? What do you see instead?
The document should be rendered as expected, or DOMPDF should error out in
a reasonable manner. On Windows, the apache child process handling the
request will die with a 3221225477 error (see the apache error.log). On
linux, the results appear to be similar, though I'm not sure if the apache
process is dying.

Prior to the end result a lot of the following duplicate errors are
recorded by PHP:
Undefined offset:  1 in dompdf\include\cellmap.cls.php on line 447

Possible relevant group posts:
http://groups.google.com/group/dompdf/browse_thread/thread/05c42dbd9fb5bc52
http://groups.google.com/group/dompdf/browse_thread/thread/edc2feff50725329

Original issue reported on code.google.com by eclecticgeek on 25 Jun 2009 at 5:43

GoogleCodeExporter commented 9 years ago

Original comment by eclecticgeek on 31 Jul 2009 at 3:40

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
The fix offered by Goldenlocks at
<http://groups.google.com/group/dompdf/msg/d3f9c0d744c93a08> is a partial 
solution.
There appear to be some further issues that need to be addressed.

Original comment by eclecticgeek on 19 Aug 2009 at 4:52

GoogleCodeExporter commented 9 years ago

Original comment by fabien.menager on 19 Jul 2011 at 8:45

GoogleCodeExporter commented 9 years ago 
I'm not entirely sure this is related to issue 91. I think this issue had more 
to do with a bug in PHP which was causing the apache child process to die. 
Issue 91 typically just results in PHP exhausting its available resources 
(memory, execution time).

This is difficult to say for sure. In the first relevant post we don't have a 
code sample. In the second I was unable to duplicate the error and the code 
sample wouldn't trigger issue 91.

As a result I don't think this bug is due to a problem with the dompdf code 
(though if we were able to pinpoint it we might have been able to mitigate the 
error).

Original comment by eclecticgeek on 15 Oct 2011 at 3:50

GoogleCodeExporter commented 9 years ago

Original comment by eclecticgeek on 30 May 2013 at 5:15