| commit | 60e9a14998bfe8666c641f7c27fec18e85ac7494 | |
| author | NRK <nrk@disroot.org> | |
| Fri, 11 Mar 2022 14:40:05 +0000 (11 20:40 +0600) | ||
| committer | Hiltjo Posthuma <hiltjo@codemadness.org> | |
| Sun, 13 Mar 2022 09:49:43 +0000 (13 10:49 +0100) | ||
| tree | 404738eeeb9b5441fb9c02a6a713342c40bea84b | treesnapshot (tar.gz zip) |
| parent | d39e2f3441fe18aba8d1a62c08918a411ec6f237 | commitdiff |
fix mem leak in cleanup()
maybe leak isn't the best word, given that the object lives for the
entire duration of the program's lifetime.
however, all elements of scheme are free-ed, can't think of any reason
why scheme itself should be an exception.
maybe leak isn't the best word, given that the object lives for the
entire duration of the program's lifetime.
however, all elements of scheme are free-ed, can't think of any reason
why scheme itself should be an exception.
| dwm.c | diffblobblamehistory |