On 10/30/22 13:36, NRK wrote:
On Sun, Oct 30, 2022 at 12:50:54PM -0700, Anskrevy wrote:
And here is my valgrind output
https://gist.github.com/Anskrevy/b981453fb7fbe3fb410ac1dd883d23ad
Looking at the backtrace it doesn't seem like it generated anywhere from
libsl (or your program)
On Sun, Oct 30, 2022 at 12:50:54PM -0700, Anskrevy wrote:
> And here is my valgrind output
> https://gist.github.com/Anskrevy/b981453fb7fbe3fb410ac1dd883d23ad
Looking at the backtrace it doesn't seem like it generated anywhere from
libsl (or your program)
==2726510== 288 (256 direct, 32
On 10/30/22 10:47, NRK wrote:
On Thu, Oct 27, 2022 at 01:19:28PM -0700, Anskrevy wrote:
Any program using libsl, or calling FcIni (directly or indirectly), that
does not call FcFini results in a small memory leak. dwm and dmenu are
effected by this.
I do not see any call to FcInit in libsl,
On Thu, Oct 27, 2022 at 01:19:28PM -0700, Anskrevy wrote:
> Any program using libsl, or calling FcIni (directly or indirectly), that
> does not call FcFini results in a small memory leak. dwm and dmenu are
> effected by this.
I do not see any call to FcInit in libsl, nor do I see any such call in
On 10/28/22 01:20, Hiltjo Posthuma wrote:
On Thu, Oct 27, 2022 at 01:19:28PM -0700, Anskrevy wrote:
Any program using libsl, or calling FcIni (directly or indirectly), that
does not call FcFini results in a small memory leak. dwm and dmenu are
effected by this. Appending a call to FcFini in the
On Thu, Oct 27, 2022 at 01:19:28PM -0700, Anskrevy wrote:
> Any program using libsl, or calling FcIni (directly or indirectly), that
> does not call FcFini results in a small memory leak. dwm and dmenu are
> effected by this. Appending a call to FcFini in the cleanup function will
> fix this.
>
Any program using libsl, or calling FcIni (directly or indirectly), that
does not call FcFini results in a small memory leak. dwm and dmenu are
effected by this. Appending a call to FcFini in the cleanup function
will fix this.
