Chore/memory writes refactor for issue #1465 #2106
Open
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 pull request introduces a
ContextProxy
to centralize and improve state management within the extension. The primary motivation is to address memory fragmentation issues caused by frequent large writes to the global state, particularly thetaskHistory
.Implementation
ContextProxy
: A new class that acts as a singleton proxy forExtensionContext.globalState
andExtensionContext.secrets
. All state access is now routed through this proxy.taskHistory
, are now stored on disk instead of in the global state. This significantly reduces memory pressure.frag-instrument.log
) has been added to track state writes and help diagnose memory fragmentation issues.ContextProxy
for better isolation and testability.Screenshots
|


|
|
How to Test
taskHistory
is stored in the global storage directory.frag-instrument.log
is created and updated.ContextProxy
is working as expected."Get in Touch
discord handle: 40ftrobot