Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
1.6.0
-
LINUX X86_64, AIX 6.1
Description
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
Attachments
Attachments
Issue Links
- blocks
-
AXIS2C-1681 Apache Axis2C Roadmap 1.7 Planning
- Open
- duplicates
-
AXIS2C-1650 memory leak xpatch.c
- Closed
- is duplicated by
-
AXIS2C-1668 Many bugs solved
- Closed
- is related to
-
AXIS2C-1602 memory leaks in xpath
- Closed