Fix memory issues by writing to temporary files instead - #82
Open
thijsnulle wants to merge 1 commit into
Open
Conversation
thijsnulle
force-pushed
the
bug/memory-issues
branch
from
April 28, 2026 08:50
da97164 to
b7374de
Compare
thijsnulle
force-pushed
the
bug/memory-issues
branch
from
April 28, 2026 08:56
b7374de to
707c9cb
Compare
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
1 participant
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 solves some issues we ran into when working with INGenious where a significantly large set of tests is ran (250+ tests with each ~1000 steps), INGenious runs out of heap space. The issue was found to be regarding the in-memory storage of several test-related logs.
As a solution, these logs have been written to temporary files and copied whenever needed.
Additionally, I refactored the
AzureSummaryHandlerand theAzureTestCaseHandlersince they also contained memory issues, but it was difficult to find exactly what the issues were without refactoring (and deleting a lot of unused code.)