Bug #76560 [Fbk->NoF]: Absurd memory allocation during PEAR step of "make install"
| From: | php-bugs at lists dot php dot net | Date: | Sun, 19 Apr 2020 04:22:04 +0000 |
| Subject: | Bug #76560 [Fbk->NoF]: Absurd memory allocation during PEAR step of "make install" | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-226661@lists.php.net to get a copy of this message | ||
Edit report at https://bugs.php.net/bug.php?id=76560&edit=1
ID: 76560
Updated by: php-bugs@lists.php.net
Reported by: php at nearlyfreespeech dot net
Summary: Absurd memory allocation during PEAR step of "make
install"
-Status: Feedback
+Status: No Feedback
Type: Bug
Package: Compile Failure
Operating System: FreeBSD
PHP Version: 7.3.0beta2
Assigned To: cmb
Private report: N
New Comment:
No feedback was provided. The bug is being suspended because
we assume that you are no longer experiencing the problem.
If this is not the case and you are able to provide the
information that was requested earlier, please do so and
change the status of the bug back to "Re-Opened". Thank you.
Previous Comments:
------------------------------------------------------------------------
[2020-04-08 11:24:07] cmb@php.net
Quite some time has passed; does this issue still persist?
------------------------------------------------------------------------
[2018-11-12 08:22:25] pascal dot christen at hostpoint dot ch
Any news here? Still persists with rc5
------------------------------------------------------------------------
[2018-08-30 09:28:56] cmb@php.net
Thanks for the update!
------------------------------------------------------------------------
[2018-08-30 01:12:24] php at nearlyfreespeech dot net
As of commit 566a75e97c7df74d3172b0b8442d857105123135 to the PHP-7.3 branch (after beta2), this
issue is still reproducible with clang, but not with gcc.
------------------------------------------------------------------------
[2018-08-29 21:55:47] cmb@php.net
There have been several FreeBSD related fixes lately, so this
issue might have been resolved. Or can anybody still reproduce
this?
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
https://bugs.php.net/bug.php?id=76560
--
Edit this bug report at https://bugs.php.net/bug.php?id=76560&edit=1