🚀 go-pugleaf

Buzz Moschetti (buzz@bear.com) wrote:
: If you hope to see your process memory usage drop by 4k when you
: deallocate during PANEL_LIST_DELETE, you won't.  Memory allocated by the
: process cannot be returned to the pool -- that's Un*x, not X or XView.

But why doesn't it get re-used? Someone else has mentioned to me that
X11R4 leaks memory. How about X11R5?

To the previous poster:

That wasn't the actual code, I always null terminate xv_set() calls.

And an OH YES (OY):

The mem leak occurs (or is more pronounced) when I use the
PANEL_LIST_FONT attribute:

xv_set(list,
       PANEL_LIST_INSERT, i, 
       PANEL_LIST_FONT, i, fixed_font, 
       PANEL_LIST_STRING, i, string, 0);

later, when the string data changes I do:

xv_set(list,
       PANEL_LIST_STRING, i, string, 0);

And the mem allocated jumps by 4k approx.

I can't convince the powers that be to get a source copy of the XView
toolkit. If only to look at what's going on internally. My guess is the
process of drawing/allocating pixmaps/whatever is messed up. They are not
being re-used.

I can understand that the list is not designed for dynamic data like this, but
what else is there in XView?

--
Opinions expressed are my own, and are not necessarily those of Bell,BCE,etc.,
or any corporation, agency or association I may be affiliated with.
  Alex Laney, Independent User Interface Guru, IWS/TRACS Project.
  Addr: xela@pinetree.org