[
https://issues.apache.org/jira/browse/AXIS2C-1702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Lazarski resolved AXIS2C-1702.
-------------------------------------
Fix Version/s: 2.0.0
(was: 1.7.0)
Resolution: Fixed
Most of the issues noted here already fixed, but there is this new one that the
patch found:
When copying HTTP output headers from msg_ctx to the response object,
the code was passing the same header pointers to both owners. This
created a latent double-free bug:
- msg_ctx owns and frees headers when destroyed
- response would try to free the same headers via out_transport_info
The bug was masked because the response memory leak prevented the
double-free from occurring. This fix:
1. Creates copies of headers before passing to response, so each owner
has its own copy to free independently
2. Fixes typo: simeple_header -> simple_header
3. Documents the response ownership model (owned by msg_ctx via
out_transport_info after attachment at line ~474)
This prepares for the 2.0.0 release with no known memory leaks.
> Memory leak in http transport
> -----------------------------
>
> Key: AXIS2C-1702
> URL: https://issues.apache.org/jira/browse/AXIS2C-1702
> Project: Axis2-C
> Issue Type: Bug
> Components: core/transport
> Affects Versions: 1.6.0
> Reporter: Bill Blough
> Priority: Minor
> Labels: patch
> Fix For: 2.0.0
>
> Attachments: memleak.patch
>
>
> Split from AXIS2C-1640
> I'm using Axis2c as a SOAP service in a project. Since there is already a
> built-in HTTP server, I was thinking whether it is possible to use that to
> provide a basic HTML GUI server in the same process that acts as SOAP server.
> I have played with this for a while and with a rather small set of changes
> this is possible (see attached patch and examples).
> At the same time while testing I encountered (using valgrind) quite a couple
> of memory leaks and a corruption - patch attached.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
