[#AXISCPP-379] Memory leaks in case of exceptions, if that happnes after Call initialize and before Call unInitialize

Axis-C++

Memory leaks in case of exceptions, if that happnes after Call initialize and before Call unInitialize

Created: 17/Jan/05 12:30 PM Updated: 20/Jan/05 05:04 PM

Return to search

Component/s:

Basic Architecture

Affects Version/s:

1.4 Final

Fix Version/s:

1.5 Alpha

Time Tracking:

Not Specified

Environment:

All (Found with Purifier on Windows)

Issue Links:

dependent

This issue is depended upon by:

~~AXISCPP-339~~ Fix trivial memory leaks revealed by profiler tools

Resolution Date:

20/Jan/05 03:48 PM

Description

« Hide

If an exception happens after Call initialize has been calld and if Call unInitialize has not been called there happens to be memory leaks.
At the moment generated code does not ensure the calling of unInitialize (only at some times it calls uninitialize)

All

Comments

Work Log

Change History

Subversion Commits

Sort Order:

Samisa Abeysinghe made changes - 17/Jan/05 12:31 PM

Field	Original Value	New Value
Assignee		Samisa Abeysinghe [ samisa ]

[ Permlink | « Hide ]

Samisa Abeysinghe added a comment - 20/Jan/05 03:48 PM

This was fixed by adding a tracking mechanism for initializing/uninitializing and added logic to uninit in the deserializer in case of exceptions.

Samisa Abeysinghe made changes - 20/Jan/05 03:48 PM

Resolution		Fixed [ 1 ]
Status	Open [ 1 ]	Closed [ 6 ]

Samisa Abeysinghe made changes - 20/Jan/05 05:04 PM

Link

This issue is depended upon by ~~AXISCPP-339~~ [ ~~AXISCPP-339~~ ]