> Perhaps comment out XChangeProperty from doing anything, see if that results in fixing it. Then we'll know whether we need to look more closely at that portion.
I did not try it yet but I believe I found another leak in XChangeProperty. When XChangeProperty is called a few times with property set to some (different) number and XGetAtomName() returns NULL, then _nxDelAllProperty only deletes the first one. Looks like nxlib combines all AtomNames = NULL into one even though they have different Atom properties. How can we fix this? This observation is based on logging all calls to XChangeProperty and _nxDelAllProperty. _nxDelProperty was not called at all. Martin --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
