wxstring, purify and memory leaks

[Willem Kokke]

sounds like user error to me.

I'm very strict on memory leaks, and found that wxWidgets in general is very
good.

I'm using wxString in alot of places, and never observed any memory leaks
occuring from them.
If you create a small example that reproduces it, i'll have a look at it if
you want.

Willem

On 30/11/06, Mickey Mestel <mickm at carmick.com> wrote:
>
>  hi,
>
>     i'm on XP, wxwidgets 2.6.3, VC++ 6, and purify.
>
>     in the main class of my program, i have a wxstring variable.  this
> variable holds coordinates of a map that is being displayed on the screen
> via a bitmap.  this variable is constantly assigned a string that are the
> coordinates of the center of the map and is then displayed when the map is
> refreshed, which is whenever you move about on the map, so that can happen
> many times a second as you are zooming in or out, any operation like that.
>
>     purify is saying that there is a memory leak here of 84 bytes, and
> there are many, many instances of this.  since this is a variable of the
> main class, which persists for the duration of the program, it certainly
> isn't a situation where the class this variable is part of is going away
> leaving allocated memory behind.
>
>     any thoughts on this?  i'm sure that widgets is not allocating new
> memory each time, and not deallocating the old memory, that is ridiculous.
> but i do need to offer an explanation for this.
>
>     thanks,
>
>     mickm
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.wxwidgets.org/pipermail/wx-users/attachments/20061204/b9e=
da8bb/attachment.htm