0001654: ERR_EMPTY_RESPONSE and "zend_mm_heap corrupted" in log

ID	Project	Category	View Status	Date Submitted	Last Update
0001654	Xdebug	Step Debugging	public	2019-04-05 10:57	2020-03-12 16:15

Reporter	hughworm	Assigned To
Priority	normal	Severity	crash	Reproducibility	always
Status	resolved	Resolution	no change required
Product Version	2.7.0

Summary	0001654: ERR_EMPTY_RESPONSE and "zend_mm_heap corrupted" in log
Description	Ubuntu 18.04 PHP 7.2.16-1+ubuntu18.04.1+deb.sury.org+1 (but also see with 7.0 and 5.6) with PhpStorm IDE. A previously working development environment stopped working after apparently upgrade of xdebug to 2.7.0. Page loads when the IDE is not listening, but when listening code breaks as expected, but empty response is returned to browser every time. Page is just calling phpinfo(). Downgraded xdebug to 2.6.0 and all works again as expected.
Steps To Reproduce	Ubuntu 18.04 Install and configure xdebug 2.7.0 Load page with no debugging: OK. Load page with debugging: Empty response and "zend_mm_heap corrupted" logged to error log.
Tags	zend_mm_heap

Operating System	Ubuntu 18.04
PHP Version	7.2.10-7.2.14

derick 2019-04-05 11:42 administrator ~0004985	I am guessing that this is the same issue as 0001647 — if you can provide a remote log file (https://xdebug.org/support.php#remote) I can check if there is a conditional breakpoint being set. The fix for this is part of Xdebug 2.7.1, which is nearly released (another hour or so), so you could try that too (it's already on pecl, so "pecl install 2.7.1.").

hughworm 2019-04-05 11:55 reporter ~0004987	Thanks. No conditional breakpoint AFAIK. I'll wait to see if 2.7.1 fixes it and send remote debugging log if not.

hughworm 2019-04-05 14:26 reporter ~0004988	I built 2.7.1 and it seems to have fixed it :) FYI There are a couple of conditional breakpoints in the project, though not on the page I was using to test.

derick 2020-03-12 16:15 administrator ~0005286	OK. Let me mark this issue as "resolved" then, as we could never really pin point this. Let me know if you see this again (in a new issue). cheers, Drick