php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #77860 zend_mm_heap corrupted
Submitted: 2019-04-06 19:47 UTC Modified: 2019-05-12 04:22 UTC
From: qiqizjlq at gmail dot com Assigned: bukka (profile)
Status: No Feedback Package: FPM related
PHP Version: 7.3.4 OS: Alpine 3.9.2
Private report: No CVE-ID: None
View Add Comment Developer Edit
Welcome! If you don't have a Git account, you can't do anything here.
You can add a comment by following this link or if you reported this bug, you can edit this bug over here.
(description)
Block user comment
Status: Assign to:
Package:
Bug Type:
Summary:
From: qiqizjlq at gmail dot com
New email:
PHP Version: OS:

 

 [2019-04-06 19:47 UTC] qiqizjlq at gmail dot com
Description:
------------
My code has reported an error in Docker. 7.3.3 7.3.4 has a recurrence. Falling back to 7.2.x is normal. But I don't know where the code is having problems. Is there any way for me to know where there is a problem?

[06-Apr-2019 19:44:30] WARNING: [pool www] child 9025 exited with code 1 after 9.724782 seconds from start
Zend_mm_heap corrupted
[06-Apr-2019 19:44:30] WARNING: [pool www] child 8981 exited with code 1 after 16.912137 seconds from start
Zend_mm_heap corrupted
[06-Apr-2019 19:44:30] WARNING: [pool www] child 9026 exited with code 1 after 9.316578 seconds from start
Zend_mm_heap corrupted
[06-Apr-2019 19:44:30] WARNING: [pool www] child 9027 exited with code 1 after 9.425341 seconds from start
Zend_mm_heap corrupted
[06-Apr-2019 19:44:30] WARNING: [pool www] child 9028 exited with code 1 after 9.456937 seconds from start
Zend_mm_heap corrupted
[06-Apr-2019 19:44:31] WARNING: [pool www] child 9029 exited with code 1 after 9.294078 seconds from start


Patches

Add a Patch

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2019-04-21 17:29 UTC] bukka@php.net
We definitely need more info. If you could attach your fpm config. Ideally please set process.dumpable and then you should be able to get core dump. If you could also add some info about the app and used extensions, that would be useful too.
 [2019-04-21 17:42 UTC] qiqizjlq at gmail dot com
hi: tks.
I have already opened process.dumpable. If there is progress, it will continue to follow up

 this is my php-fpm conf:
[global]
error_log = /proc/self/fd/2

; https://github.com/docker-library/php/pull/725#issuecomment-443540114
log_limit = 8192

[www]
; if we send this to /proc/self/fd/1, it never appears
access.log = /proc/self/fd/2

clear_env = no

; Ensure worker stdout and stderr are sent to the main error log.
catch_workers_output = yes
decorate_workers_output = no

[global]
error_log = /proc/self/fd/2
log_level = warning
emergency_restart_threshold = 30
emergency_restart_interval = 60s
process_control_timeout = 5s


[www]
access.log = /proc/self/fd/1
;listen = 127.0.0.1:9000
user = www-data
group = www-data
pm = dynamic
pm.max_children = 70
pm.start_servers = 30
pm.min_spare_servers = 30
pm.max_spare_servers = 70
pm.max_requests = 1000

request_terminate_timeout = 120
request_slowlog_timeout = 2s
slowlog = /proc/self/fd/2
rlimit_files = 51200
rlimit_core = 0


[global]
daemonize = no

[www]
listen = 9000

this is my php-ext enable:

[PHP Modules]
Core
ctype
curl
date
dom
fileinfo
filter
ftp
gd
hash
iconv
json
libxml
mbstring
mysqli
mysqlnd
openssl
pcre
PDO
pdo_mysql
pdo_sqlite
Phar
posix
readline
redis
Reflection
session
SimpleXML
sodium
SPL
sqlite3
standard
tokenizer
xml
xmlreader
xmlwriter
Zend OPcache
zlib

[Zend Modules]
Zend OPcache
 [2019-04-28 18:29 UTC] bukka@php.net
-Status: Open +Status: Feedback -Assigned To: +Assigned To: bukka
 [2019-04-28 18:29 UTC] bukka@php.net
Config looks ok so without core dump or re-creatable piece of code there is not much we can I'm afraid.

I will set status to Feedback which will close itself in 2 weeks or so if there is no further info. But we can always re-open it if you manage to get more info ;)
 [2019-05-12 04:22 UTC] php-bugs at lists dot php dot net
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.
 
PHP Copyright © 2001-2019 The PHP Group
All rights reserved.
Last updated: Sun Nov 17 06:01:40 2019 UTC