This is the mail archive of the guile@cygnus.com mailing list for the guile project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Jon Trowbridge <trow@emccta.com> writes: > Is there anything that I can do to trigger an "aggressive" garbage > collection in guile, in which the whole heap would be scanned and I > could be sure afterwards that every lingering unreferenced object had > been deallocated? That is how the gc currently operates (though I might not be understanding you correctly). If a dead object is hanging around, it means that either it's being scanned conservatively, or that something you don't know about is holding a reference to it (the printer is currently very bad in this regard). > I don't mind if this is a relatively slow operation --- lingering > unreferenced smobs are making it impossible for me to > deterministically flush some caches in the C++ back-end that I'm using > guile to scriptify... -- Greg