Bug #77955 [Com]: Random segmentation fault in mysqlnd from php-fpm
| From: | victoria at sharksmedia dot dk | Date: | Mon, 08 Jul 2019 11:14:28 +0000 |
| Subject: | Bug #77955 [Com]: Random segmentation fault in mysqlnd from php-fpm | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-221655@lists.php.net to get a copy of this message | ||
Edit report at https://bugs.php.net/bug.php?id=77955&edit=1
ID: 77955
Comment by: victoria at sharksmedia dot dk
Reported by: victoria at sharksmedia dot dk
Summary: Random segmentation fault in mysqlnd from php-fpm
Status: Closed
Type: Bug
Package: PDO MySQL
Operating System: CentOS 7.6.1810
PHP Version: 7.3.4
Assigned To: dmitry
Block user comment: N
Private report: N
New Comment:
Hi,
I'm just writing to confirm that the segmentation fault is gone with php 7.3.7.
But there seem to be massive memory leaks still present, i'm still getting the "Allowed
memory size of x bytes exhausted", very quickly in longer running scripts such as cronjobs.
I'm isolating the problem, and posting a new bug.
Thanks for fixing this one though :)
Previous Comments:
------------------------------------------------------------------------
[2019-06-03 07:56:07] scott at exussum dot co dot uk
Hi Dmitry / Nikita
That fix has changed something we now get
terminated by signal SIGSEGV (Address boundary error)
It terminates at a similar place though.
Anything I can do to help debug this further ?
------------------------------------------------------------------------
[2019-06-03 07:16:10] dmitry@php.net
The fixes are going to stay in all versions. Confirmation is not necessary. If you'll see the
problem - reopen the bug report.
It's not possible to run different PHP components, built in different "debug" mode.
------------------------------------------------------------------------
[2019-06-03 06:02:36] victoria at sharksmedia dot dk
Hi Dmitry
I see the fixes weren't inclded in 7.3.6.
Will they be in 7.3.7, or do you need to have confirmation of it working before it is included in
the release?
As mentioned, i can't "just" run a debug build, as remi doesn't provide it and
wont help make one.
Can i compile a debug version of the php binary, and mysqlnd.so, and use that with all the
extensions not compiled in debug mode?
Or must ALL loaded binaries be compiled in the same debug mode?
Because, than i can just compile php, and replace the two binaries on the production server without
messing more with the production setup.
------------------------------------------------------------------------
[2019-05-24 05:24:42] victoria at sharksmedia dot dk
That looks good.
Will this fix be in 7.3.6?
Since we're using the remi repo, it is quite a task to compile it all to be a direct swapable
replacement (Remi couldn't provide info on how to compile his SRPMS)
------------------------------------------------------------------------
[2019-05-23 15:12:05] dmitry@php.net
Most probably, the bug is fixed by https://github.com/php/php-src/commit/6f9dfd947302f9a0d2fa6a78bf385b1ca7dafdf3
Victoria, it would be great if you could test your app, using DEBUG build of PHP-7.3 snapshot.
------------------------------------------------------------------------
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=77955
--
Edit this bug report at https://bugs.php.net/bug.php?id=77955&edit=1