Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!crdgw1!uakari.primate.wisc.edu!zaphod.mps.ohio-state.edu!sdd.hp.com!hp-pcd!hpcvlx!bturner
From: bturner@hpcvlx.cv.hp.com (Bill Turner)
Newsgroups: comp.windows.x
Subject: Re: SCO Motif 1.0 problems (SCO has no plans to fix these)
Message-ID: <100920321@hpcvlx.cv.hp.com>
Date: 28 May 91 23:46:12 GMT
References: <1991May24.172352.23135@grebyn.com>
Organization: Hewlett-Packard Co., Corvallis, OR, USA
Lines: 24

>a.     create a Label widget;
>
>b.     change the Label widgets string once every few seconds using
>       XtSetValues;
>
>c.     let it cook for some hours.

I'm not sure about SCO's implementation, but the HP Motif 1.0 Label
widget (and for that matter any other widget that gets XmStrings as
resource values) makes a copy of the XmString ("I can't depend on this
value being valid later, I'll make a copy of it so I know it's good.").

Are you calling XmStringFree after you XtSetValues of the Label?  If
not, you should be -- this would cause the leak.

    XmString tcs;

    tcs = XmStringCreateLtoR("string for label", XmSTRING_DEFAULT_CHARSET);
    XtSetArg(args[n], XmNlabel, tcs); n++;
    XtSetValues(label_widget, args, n);
    XmStringFree(tcs);

--Bill Turner (bturner@hp-pcd.cv.hp.com)
HP Interface Technology Operation