fix for issue #660 where the call to llama_batch_free is failing during process shutdown #734
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
llama_batch_free is failing during python shutdown when the interpreter can set objects to None non-deterministically. I believe Guidance is properly checking for None in the objects that can be accessed from Guidance, but llama-cpp-python is not, and the native library object in llama-cpp-python is being set to None before it can be called. Since we're only dealing with memory deallocation here, and since the process is being killed anyway, we can solve this on the Guidance side by not calling llama_batch_free during process termination.