3 ms·
> It's the community widgets that tend to have memory leak problems, not the core package. As mentioned, this seems to be a quirk in how Lua and GTK interact (m
by Zurrrrr 4y ago
> It's the community widgets that tend to have memory leak problems, not the core package. As mentioned, this seems to be a quirk in how Lua and GTK interact (many community widgets use GTK).
What widgets are you referring to that you found to have leaks?
> You'll just have to take my word for it when I tell you that I've tried very hard and for a very long time.
It's just that it seems to contradict most of the other reports I've seen, but then I don't care about stacking myself, so ok.
> I wouldn't really call AwesomeWM exceptionally user-friendly. The docs are good. The API is good. It's developer-friendly, certainly, but that's as far as the ease-of-use goes.
I said it was user-friendly for what it is. There is nothing else really like it that allows that level of extensibility, and given how it abstracts so much complexity, I would say they did indeed do a good job of making it user friendly. Again though, that's keeping in mind what it is. It isn't trying to be i3/xfce/etc or as user-friendly as those.
- chaorace 4y ago> What widgets are you referring to that you found to have leaks? I'll cite myself here: https://github.com/streetturtle/awesome-wm-widgets/issues/11#issuecomment-1185946301 https://github.com/streetturtle/awesome-wm-widgets/issues/11... Here's another affected library [1]: https://github.com/deficient/volume-control https://github.com/deficient/volume-control I've had similar issues wherever GTK interacts with awful.spawn. Basically: glib (GTK) + awful.spawn.easy_async + polling = extremely leak-prone. This is a very common pattern in community awesomewm widgets. [1]: No bug under the main repo because they're considering it as a framework bug. See here for discussion: https://github.com/awesomeWM/awesome/issues/3584#issuecomment-1247669362 https://github.com/awesomeWM/awesome/issues/3584#issuecommen...