bug#15602: bug#19235: make-fresh-user-module procedure leaks memory

2016-06-25 Thread Mark H Weaver
l...@gnu.org (Ludovic Courtès) writes: > Mark H Weaver skribis: > >> One potential issue that has been troubling me is that in Guile's model, >> there's no guarantee that a module will _ever_ finish loading. > > I think the fact that we evaluate all the top-level forms is >

bug#19235: make-fresh-user-module procedure leaks memory

2016-06-24 Thread Ludovic Courtès
Mark H Weaver skribis: > Andy Wingo writes: > >> In many ways I think Ludovic was right in #15602 -- we should allow >> excursions to isolate changes to the module tree. Sometimes you want an >> excursion to never add a module to the tree. Sometimes you do,

bug#19235: make-fresh-user-module procedure leaks memory

2016-06-23 Thread Mark H Weaver
Andy Wingo writes: > In many ways I think Ludovic was right in #15602 -- we should allow > excursions to isolate changes to the module tree. Sometimes you want an > excursion to never add a module to the tree. Sometimes you do, but > maybe all in one go and with a mutex, to

bug#19235: make-fresh-user-module procedure leaks memory

2016-06-22 Thread Andy Wingo
In many ways I think Ludovic was right in #15602 -- we should allow excursions to isolate changes to the module tree. Sometimes you want an excursion to never add a module to the tree. Sometimes you do, but maybe all in one go and with a mutex, to avoid races -- like, you could load a file or

bug#19235: make-fresh-user-module procedure leaks memory

2014-12-26 Thread Chris Vine
As far as I can tell the make-fresh-user-module procedure is not called by guile itself, and providing a global mutex for it with a binding enabling it to be called from scheme code seems to work fine. This also makes it straightforward to incorporate in a thread-safe way the code you suggested

bug#19235: make-fresh-user-module procedure leaks memory

2014-12-07 Thread Mark H Weaver
Chris Vine ch...@cvine.freeserve.co.uk writes: The make-fresh-user-module procedure leaks memory in guile-2.0.11 as demonstrated by the attached test case. [...] The question which might be asked is Would any sane person ever want to invoke the make-fresh-user-module procedure more than a

bug#19235: make-fresh-user-module procedure leaks memory

2014-12-07 Thread Chris Vine
On Sun, 07 Dec 2014 03:07:43 -0500 Mark H Weaver m...@netris.org wrote: Chris Vine ch...@cvine.freeserve.co.uk writes: The make-fresh-user-module procedure leaks memory in guile-2.0.11 as demonstrated by the attached test case. [...] The question which might be asked is Would any sane

bug#19235: make-fresh-user-module procedure leaks memory

2014-11-30 Thread Chris Vine
The make-fresh-user-module procedure leaks memory in guile-2.0.11 as demonstrated by the attached test case. This test case should be invoked either with the shared or fresh option. If invoked with the fresh option, it will call make-fresh-user-module on each iteration through the loop. On my