On further investigation, it appears that accumulation of waste does not trigger next generation garbage collection.
Thus programs with a high Waste-to-Alloc ratio and regular calls to (gc :full nil) can trigger HEAP-EXHAUSTED-ERROR or crashes to ldb.
I wonder if any of the following statements are true:
1) foreign function calls are creating waste (such as requesting a collection through (gc))
2) the (gc :full nil) implementation is broken or incomplete
On further investigation, it appears that accumulation of waste does not trigger next generation garbage collection.
Thus programs with a high Waste-to-Alloc ratio and regular calls to (gc :full nil) can trigger HEAP-EXHAUSTED- ERROR or crashes to ldb.
I wonder if any of the following statements are true:
1) foreign function calls are creating waste (such as requesting a collection through (gc))
2) the (gc :full nil) implementation is broken or incomplete