[
https://issues.apache.org/jira/browse/AXIS2C-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Lazarski resolved AXIS2C-1669.
-------------------------------------
Fix Version/s: 2.0.0
(was: 1.7.0)
Resolution: Fixed
[~billblough] I evaluated the remaining issues with Claude Code and the
suggestion is to close this issue, so I am taking that action here though feel
free of course to re-open.
AXIS2C-1669 can be closed. 6 of 11 patches have been applied. The remaining 4
patches were evaluated and found to have issues:
- op_client.c.patch: Contains a bug - conditional engine free causes memory
leak on success path (AXIS2_SUCCESS=0)
- ssl_utils.c.patch: Would break server SSL - changing BIO_NOCLOSE to
BIO_CLOSE needs client/server detection
- http_sender.c.patch: Mixed quality - some valid fixes but also bugs in
connection_map handling
- libxml2_reader_wrapper.c.patch: Low priority cosmetic fix
The core memory leak issues from the original patches have been addressed.
The remaining patches need redesign or contain bugs that would introduce new
issues.
> Misc patches for mem leak, REST Call, SSL, XPATH
> ------------------------------------------------
>
> Key: AXIS2C-1669
> URL: https://issues.apache.org/jira/browse/AXIS2C-1669
> Project: Axis2-C
> Issue Type: Bug
> Components: core/engine
> Affects Versions: 1.6.0
> Environment: LINUX X86_64, AIX 6.1
> Reporter: Jean-Marc Lamond
> Assignee: Bill Blough
> Priority: Major
> Labels: patch
> Fix For: 2.0.0
>
> Attachments: Consolidated.patch, http_sender.c.patch,
> http_transport_utils.c.patch, libxml2_reader_wrapper.c.patch,
> op_client.c.patch, options.c.patch, ssl_utils.c.patch, xpath.c.patch,
> xpath_internals_engine.c.patch, xpath_internals_parser.c.patch,
> xpath_streaming.c.patch
>
> Original Estimate: 120h
> Remaining Estimate: 120h
>
> Dear Mr. Mantaut,
> Late 2013, I had submit some patches that you reject because of other mem
> leak induced by my work. I did follow your guidance and used valgrind to help
> me debug the mem leak problem from XPATH and Client API.
> I solved all my case early january 2014 but never took the time to upload my
> clean patches.
> I have a sample program that I can send you to reproduce mem leak from the
> current trunk if you need so.
> Please find attached following patches:
> Consolidated.patch - all patches
> http_sender.c.patch - mem leak + REST + "check your log and buffer"
> *APPLIED* http_transport_utils.c.patch - mem leak
> libxml2_reader_wrapper.c.patch - error
> op_client.c.patch - mem leak
> *APPLIED* options.c.patch - mem leak
> ssl_utils.c.patch - design problem between client end server socket handling
> *APPLIED* xpath.c.patch - mostly printf to log and mem leak
> *APPLIED* xpath_internals_engine.c.patch - mem leak
> *APPLIED* xpath_internals_parser.c.patch - mem leak
> *APPLIED* xpath_streaming.c.patch - mem leak
> Best regards,
> Jean-Marc
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
