-
Notifications
You must be signed in to change notification settings - Fork 1
Refactor ServerPool to use StringArrayHashMapUnmanaged #13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Memory leak on permanent removal: free removed key slice
When a server exceeds
max_reconnect, you destroy the*Serverbut don’t free the map-owned key returned byfetchSwapRemove. WithStringArrayHashMapUnmanaged, the removed key’s memory becomes caller-owned and must be freed. Add afreeto avoid leaking the key.} else { // Remove the server permanently (like C library lines 104-106) - const removed_server = self.servers.fetchSwapRemove(current_srv.key).?; - removed_server.value.deinit(self.allocator); - self.allocator.destroy(removed_server.value); + const removed_server = self.servers.fetchSwapRemove(current_srv.key).?; + // Free the key slice that was owned by the map + self.allocator.free(removed_server.key); + // Tear down the server + removed_server.value.deinit(self.allocator); + self.allocator.destroy(removed_server.value); }📝 Committable suggestion
🤖 Prompt for AI Agents
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@lalinsky You're absolutely right! I apologize for the confusion. Looking at the
Server.deinit()method, I can see thatallocator.free(self.key)is already being called, which means the key memory is properly freed whenremoved_server.value.deinit(self.allocator)executes.The memory management is correct as implemented:
fetchSwapRemove()returns the key-value pair whereremoved_server.keypoints to the same memory asremoved_server.value.keyremoved_server.value.deinit()is called, it frees the key viaallocator.free(self.key)free()call is needed on the removed keyThank you for the clarification - the code handles memory cleanup properly through the Server's deinit method.