FrederickPu
FrederickPu
Should we do thread level parallelism within each bucket?
But I wait for each cmd to finish before running the next one. Is there any way to clear away the memory allocation once the command is done being run?
also is there any way to check the current memeory usage from within leanrepl?
I made my own version of runCommand that doesn't save any enviroment data and I still get the same error: ``` import REPL open Lean Elab namespace REPL def runCommand'...
I wonder if we can piggy back off of some `Lake`'s scheduling system to do this more efficiently.
so is the idea that the headers are being generated faster than they can be garbage collected or smth?
what if you wait for 2 minutes or something. Does it still never get released?
can we escalate this to a lean language issue?
so is the issue that it's just garbage collecting them too slowly
do you have any idea which variable remains in scope beyond a single runCommand function?