Bug #63950 [Com]: Lot's of memory leaks detected
| From: | hufeng1987 at gmail dot com | Date: | Thu, 10 Jan 2013 06:36:34 +0000 |
| Subject: | Bug #63950 [Com]: Lot's of memory leaks detected | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-175927@lists.php.net to get a copy of this message | ||
Edit report at https://bugs.php.net/bug.php?id=63950&edit=1
ID: 63950
Comment by: hufeng1987 at gmail dot com
Reported by: hufeng1987 at gmail dot com
Summary: Lot's of memory leaks detected
Status: Feedback
Type: Bug
Package: FPM related
Operating System: CentOS 5.8
PHP Version: 5.4.10
Block user comment: N
Private report: N
New Comment:
I tried upgrade apc to 3.1.14. but failed at make test
-------------------------------------------------------------------------
=====================================================================
TIME END 2013-01-10 14:34:30
=====================================================================
TEST RESULT SUMMARY
---------------------------------------------------------------------
Exts skipped : 0
Exts tested : 42
---------------------------------------------------------------------
Number of tests : 56 55
Tests skipped : 1 ( 1.8%) --------
Tests warned : 0 ( 0.0%) ( 0.0%)
Tests failed : 6 ( 10.7%) ( 10.9%)
Expected fail : 0 ( 0.0%) ( 0.0%)
Tests passed : 49 ( 87.5%) ( 89.1%)
---------------------------------------------------------------------
Time taken : 39 seconds
=====================================================================
=====================================================================
FAILED TEST SUMMARY
---------------------------------------------------------------------
APC: classes with namespaces (php 5.3) [tests/apc53_001.phpt]
APC: global spaces (php 5.3) [tests/apc53_002.phpt]
APC: closures (php 5.3) [tests/apc53_004.phpt]
APC: apc_store/fetch with objects [tests/apc_002.phpt]
APC: apc_store/fetch with objects (php 5.3) [tests/apc_003b.phpt]
APC: APCIterator formats [tests/iterator_006.phpt]
=====================================================================
You may have found a problem in PHP.
This report can be automatically sent to the PHP QA team at
http://qa.php.net/reports and http://news.php.net/php.qa.reports
This gives us a better understanding of PHP's behavior.
If you don't want to send the report immediately you can choose
option "s" to save it. You can then email it to qa-reports@lists.php.net later.
Do you want to send this report now? [Yns]: Y
Please enter your email address.
(Your address will be mangled so that it will not go out on any
mailinglist in plain text): hufeng1987@gmail.com
Posting to http://qa.php.net/buildtest-process.php
Thank you for helping to make PHP better.
Previous Comments:
------------------------------------------------------------------------
[2013-01-10 06:23:05] hufeng1987 at gmail dot com
After disabled APC extension. the memory leaks reporting stopped. what is the
matter?
we really need APC , production environment need APC to boost the PHP
performanceï¼
------------------------------------------------------------------------
[2013-01-10 05:58:00] pajoye@php.net
Disable APC and try again, that will clear this last question.
------------------------------------------------------------------------
[2013-01-10 05:10:48] laruence@php.net
it depends on what the codes is, and whether it is a known issue.
------------------------------------------------------------------------
[2013-01-10 04:46:55] hufeng1987 at gmail dot com
i have configured the core dump environment. still waiting for the core dump. it's
not always segfault, i hope i could catch it .
I want to ask, if some code cause php segfault, it's code's problem or the php's
problem?
should we fixed it by change the code ? or need to fixed by php upstream?
------------------------------------------------------------------------
[2013-01-10 04:42:43] laruence@php.net
could you please give us the backtrace of the segfault you mentioned?
------------------------------------------------------------------------
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=63950
--
Edit this bug report at https://bugs.php.net/bug.php?id=63950&edit=1