search

sdglhm / dompdf

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

xdebug and PHP code for header/footer kills output when streaming #381

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. installed xdebug in Ubuntu 10.04
2. added a <script type="text/php">/script> block after the <body> tag
3. tried to stream the PDF for download

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

Expected to be prompted to save PDF but got the following message in Chrome:

Error 324 (net::ERR_EMPTY_RESPONSE) 

What version of the product are you using? On what operating system?

Using 0.6.0 beta, also tested with 0.5.2.

Environment is Ubuntu 10.04 LTS with Apache/2.2.14, PHP 5.3.2

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

I confirmed that xdebug was contributing to the problem by uninstalling, 
testing, re-installing, and testing again.

Original issue reported on code.google.com by dvog...@islandlinux.org on 22 Nov 2011 at 8:56

GoogleCodeExporter commented 9 years ago 
I am facing the same issue while generating pdf from HTML.I am using dompdf and 
when I am converting HTML to pdf it is showing an error.

No Data Received
Error 324 (net::ERR_EMPTY_RESPONSE) 

On other browsers it gives a blank screen.

Pls let me know if any one is having same issue and have solution to it.

Original comment by saumil.2...@gmail.com on 21 Dec 2011 at 3:40

GoogleCodeExporter commented 9 years ago 
@saumil.21188, are you using xdebug?

Original comment by dvog...@islandlinux.org on 21 Dec 2011 at 8:52

GoogleCodeExporter commented 9 years ago 
I've been getting the same error (connection reset or Error 324)

No errors in any logs but dompdf was falling over at the ->render() stage

When I removed the table from my html -> no more error, pdf downloaded fine.

Don't know if this is the cause for other cases (and it must still count as a 
defect) but removing this helped me.

Original comment by edworm...@gmail.com on 22 Feb 2012 at 12:54

GoogleCodeExporter commented 9 years ago 
I have also noticed that there is a segfault in apache2 that shows up in the 
apache2 error log:

[notice] child pid 850 exit signal Segmentation fault (11)

Original comment by dvog...@islandlinux.org on 28 Mar 2012 at 2:25

GoogleCodeExporter commented 9 years ago

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