Fix memory leaks in crash and memleak endpoints#59
Draft
Conversation
Co-authored-by: mrsharm <68247673+mrsharm@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Memory Analysis: High Heap Usage by System.String in cpu-app (memleak and crash endpoints)
Fix memory leaks in crash and memleak endpoints
Jul 15, 2025
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
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 PR addresses critical memory issues identified in the Azure SRE Agent memory analysis that were causing high heap usage from
System.Stringallocations and potential application crashes.Issues Fixed
1. Infinite Loop in
crashEndpointProblem: The while condition
while (true || bytesSize < 1_000_000)created an infinite loop due to the OR operator always evaluating to true, causing unlimited memory allocation.Fix: Changed to
while (bytesSize < 1_000_000)to respect the intended 1MB limit.2. Memory Accumulation in
memleakEndpointProblem: The static
Processorinstance accumulatedCustomerobjects indefinitely across requests, with each Customer containing a GUID string, leading to excessive string allocations and memory retention.Fix: Added cache clearing after each request to prevent indefinite accumulation while preserving the endpoint's intended functionality.
Changes Made
Clear()andCountmethods toCustomerCacheclassClearCache()andCacheCountmethods toProcessorclassImpact
Testing
All endpoints tested and verified:
crashendpoint now terminates properly (was infinite loop)memleakendpoint processes requests with memory cleanupappinvokeendpoint continues working as expectedFixes #58.
💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.