Re: Yet another leak in Xlib

2022-10-03 Thread Po Lu
Thomas Dickey writes: > looks okay reading the library code (src/xlibi18n/XDefaultIMIF.c, _CloseIM). > > xterm doesn't free that 'xim' value (and the XCloseIM manual page doesn't > say who's responsible for that -- though it's possible that some other > application developer read the library

Re: Yet another leak in Xlib

2022-10-03 Thread Thomas Dickey
On Mon, Oct 03, 2022 at 06:47:32PM +0800, Po Lu wrote: > Po Lu writes: > > > ==67186== 408 bytes in 1 blocks are definitely lost in loss record 272 of > > 344 > > ==67186==at 0x484A464: calloc (vg_replace_malloc.c:1328) > > ==67186==by 0x490935F: _XimOpenIM (in

Re: Yet another leak in Xlib

2022-10-03 Thread Po Lu
Po Lu writes: > ==67186== 408 bytes in 1 blocks are definitely lost in loss record 272 of 344 > ==67186==at 0x484A464: calloc (vg_replace_malloc.c:1328) > ==67186==by 0x490935F: _XimOpenIM (in /usr/lib64/libX11.so.6.4.0) > ==67186==by 0x490F386: _XimRegisterIMInstantiateCallback (in