Fix GC finalization cycle in SNI callback implementation #1561
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.
Summary
finalizemethodProblem
The SNI callback implementation was causing "GC Warning: Finalization cycle involving (???)" warnings during specs. This occurred because:
@sni_callback_boxSolution
Changed callback storage from instance variables to class-level hash:
@@sni_callback_boxesstores boxes keyed by context handlefinalizemethod to explicitly free callback boxes and clean up storageTest plan
make test SPEC=spec/sni_spec.cr- 10 examples, 0 failures, 0 GC warningsmake test SPEC=spec/stdlib/openssl_keylog_spec.cr- 0 GC warnings🤖 Generated with Claude Code