Thanks for your reply. Le jeu. 16 mai 2019 à 03:41, Mark H Weaver <m...@netris.org> a écrit :
> Amirouche Boubekki <amirouche.boube...@gmail.com> writes: > > > I am stuck with a memory leak. I think gc-live-object-stats [0] would > help. > > > > [0] > https://www.gnu.org/software/guile/manual/html_node/Garbage-Collection-Functions.html#index-gc_002dlive_002dobject_002dstats > > > > Can some explain to me how to bring it back? > > Personally, I suggest finding another approach to debug your leak. > > I don't want to spend much time on this, because I suspect it would be a > lot of work for questionable benefit, and it's not clear whether the > result of that work will be acceptable to either libgc or Guile. It > might introduce too much added complexity or overhead. > Then it would be preferable to remove it from the manual. My understanding of how GC works makes unlikely there is a leak in the Guile code except particular cases that I don't know about, but I tested some of those. For instance, dynamic-func pointers are collected. Also while experimenting with the official Python bindings, I discovered that I did not setup proper eviction configuration which leads to something that looks like a leak. In fact, it is just that wiredtiger can not keep up with the batch load in the default configuration. Anyway, Thanks!
