I'm currently debugging a memory leak, and I suspect that it's in my native code, not s7; however, i'd like to rule s7 out as well as figure out if there's some reference chain that's keeping the GC from doing its job. Also, it would probably make valgrind happy to clean up s7's state.
On 2019-12-30 13:21:33-05:00 [email protected] wrote: The question has come up before, but I'm not sure it was in cmdist. I don't know how to search the archives. There's currently no way to destroy the interpreter and free its resources. I think it would be easy to release most of them (the heap etc), but a complete cleanup would take some effort. Why do you need this?
_______________________________________________ Cmdist mailing list [email protected] https://cm-mail.stanford.edu/mailman/listinfo/cmdist
