Create multitenant_memory_manager.go (closes #206) #207
+563
−0
Conversation
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 commit implements the proposal from issue Exafunction#206 by @RAPIDENN. - Solves: - Exafunction#63: memory leak (by limiting and cleaning memory usage) - Exafunction#176: too many open files (via per-namespace constraints)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This commit implements the proposal from issue #206.
Implements per-user and per-project namespace isolation with memory limits, LRU eviction, and automatic cleanup after inactivity.
This change addresses a class of long-standing issues caused by unscoped memory and file descriptor usage in multi-session environments. It also prevents known edge cases such as hitting the 1024 FD limit in glibc’s
select()implementation—an issue widely discussed by developers due to how it silently breaks applications when the descriptor count exceeds the hardcodedFD_SETSIZE. These bugs are notoriously difficult to trace and have led to crashes, corrupted state, and even exploitation in CTF challenges.The new memory manager integrates with the language server via a
LanguageServerExtensionand requires minimal changes to the surrounding codebase. It improves scalability, stability, and memory safety in high-concurrency environments by ensuring each user/project session operates independently with enforced limits.