[xsd-users] memory not deallocated ?

[Boris Kolpackov]

frederic heem <frederic.heem at telsey.it> writes:

> When program is executed under the control of valgrind, it shows that some
> memory hasn't been deallocated. I reckon this memory is allocated once for
> the whole life of the program, so it may be NOT a memory leak. However, I
> do  prefer having a program which deallocate everything so that "real"
> memory leak can be detected quicker.

What you see is a type factory map which is created during static object
initialization and is there for the life-time of the program. I guess
you are right and it is better to destroy it if only to keep memory
checkers at bay. I will fix this for the release.

hth,
-boris
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 652 bytes
Desc: Digital signature
Url : http://codesynthesis.com/pipermail/xsd-users/attachments/20051031/026db528/attachment.pgp