Open jcbritobr opened 1 year ago
You're absolutely correct. gtkcord4 has had a memory leak since the start; it mostly has to do with the internal weak reference code breaking and I don't have any way of debugging why that happens.
If anyone could fix this on gotk4's side, that would be awesome. I think the new runtime.Pinner
API will help a lot but that would require refactoring the internal code and I haven't had the time to do that yet.
Memory usage seems to go very high also when opening a channel with many images.
I'm using gtkcord and its working very well, but notice that the resources allocated keep going allocated even when you got a repeated page, and they aren't collected. Memory got high easy only changing pages, and even the same pages.