php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login

go to bug id or search bugs for

Bug #78039 Huge memory leak when soap fault
Submitted: 2019-05-20 09:59 UTC Modified: 2021-04-04 04:22 UTC
Votes:4
Avg. Score:4.2 ± 0.8
Reproduced:3 of 3 (100.0%)
Same Version:2 (66.7%)
Same OS:1 (33.3%)
From: n0dwis at gmail dot com Assigned: cmb (profile)
Status: No Feedback Package: SOAP related
PHP Version: 7.2.18 OS: Alpine Linux
Private report: No CVE-ID: None
View Developer Edit
Welcome! If you don't have a Git account, you can't do anything here.
If you reported this bug, you can edit this bug over here.
(description)
Block user comment
Status: Assign to:
Package:
Bug Type:
Summary:
From: n0dwis at gmail dot com
New email:
PHP Version: OS:

 

 [2019-05-20 09:59 UTC] n0dwis at gmail dot com 
Description:
------------
When Soap call finished with error memory_get_usage shows increasing memory usage to 30Mb. This memory don't free in next requests.
This is short log
Before call soap 8MB
Soap fault
After call soap 46MB
Before call soap 46MB
Soap fault
After call soap 72MB
Before call soap 72MB
Soap fault
After call soap 100MB
Before call soap 100MB
Soap fault
After call soap 128MB

And this is log without failing. Memory leak exist too but not so big
Before call soap 8MB
After call soap 36MB
Before call soap 38MB
After call soap 38MB
Before call soap 38MB
After call soap 38MB
Before call soap 38MB
After call soap 40MB
Before call soap 38MB
After call soap 40MB
Before call soap 40MB
After call soap 40MB
Before call soap 40MB
After call soap 40MB
Before call soap 38MB
After call soap 40MB
Before call soap 38MB
After call soap 40MB
Before call soap 40MB
After call soap 40MB
Before call soap 40MB
After call soap 40MB
Before call soap 38MB
After call soap 40M

This behaviour is in a php docker container 7.2.9 and 7.2.18

Patches

Pull Requests

Pull requests:

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2019-05-20 09:59 UTC] requinix@php.net
-Status: Open +Status: Feedback
 [2019-05-20 09:59 UTC] requinix@php.net 
Thank you for this bug report. To properly diagnose the problem, we
need a short but complete example script to be able to reproduce
this bug ourselves. 

A proper reproducing script starts with <?php and ends with ?>,
is max. 10-20 lines long and does not require any external 
resources such as databases, etc. If the script requires a 
database to demonstrate the issue, please make sure it creates 
all necessary tables, stored procedures etc.

Please avoid embedding huge scripts into the report.
 [2019-05-30 21:04 UTC] n0dwis at gmail dot com
-Status: Feedback +Status: Open
 [2019-05-30 21:04 UTC] n0dwis at gmail dot com 
I tried but I can't reproduce it in test environment. It's no any leak if I use simple test Soap services. This happen only in our production environment.
I understand it hard to figure out the bug, but I can't provide more information. Sorry.
 [2019-07-15 13:23 UTC] nikic@php.net 
I've done some changes in 7.4 that may fix or reduce this leak.
 [2019-08-15 00:21 UTC] rrpds1994 at gmail dot com 
The following pull request has been associated:

Patch Name: Fix #77728: pgort140.DLL missing
On GitHub:  https://github.com/php/web-rmtools/pull/6
Patch:      https://github.com/php/web-rmtools/pull/6.patch
 [2019-08-15 00:24 UTC] rrpds1994 at gmail dot com 
The following pull request has been associated:

Patch Name: improves lookup-hack wrt. mysqli_stmt and mysqli_driver (fixes #66340)
On GitHub:  https://github.com/php/systems/pull/4
Patch:      https://github.com/php/systems/pull/4.patch
 [2021-03-23 14:20 UTC] cmb@php.net
-Status: Open +Status: Feedback -Assigned To: +Assigned To: cmb
 [2021-03-23 14:20 UTC] cmb@php.net 
> I've done some changes in 7.4 that may fix or reduce this leak.

So, can you still reproduce this with any of the actively
supported PHP versions[1]?

[1] <https://www.php.net/supported-versions.php>
 [2021-04-04 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-2025 The PHP Group
All rights reserved. 		Last updated: Thu Jul 17 01:01:33 2025 UTC