Skip to content

Fixed memory leak in ArchRule.AssertionError in combination with JUnit 4#123

Merged
codecholeric merged 1 commit into
masterfrom
fix-assertionerror-mem-leak
Nov 20, 2018
Merged

Fixed memory leak in ArchRule.AssertionError in combination with JUnit 4#123
codecholeric merged 1 commit into
masterfrom
fix-assertionerror-mem-leak

Conversation

@codecholeric

Copy link
Copy Markdown
Collaborator

The chain JUnit 4 Core -> Failure -> ArchRule.AssertionError -> EvaluationResult causes (sometimes huge) EvaluationResults to be hard-referenced through the whole JUnit run, which was never intended (original design error due to the assumption, that an AssertionError would be something transient).

This PR removes ArchRule.AssertionError (causing a breaking change)

@codecholeric codecholeric added this to the 0.9.3 milestone Nov 20, 2018
…es keep reference to the respective AssertionError, ArchRule.AssertionError kept reference to EvaluationResult, thus making it impossible to GC big results over the whole JUnit run.

Signed-off-by: Peter Gafert <peter.gafert@tngtech.com>
@codecholeric codecholeric force-pushed the fix-assertionerror-mem-leak branch from ec61b97 to 8b859a4 Compare November 20, 2018 15:56
@codecholeric codecholeric merged commit 83583ee into master Nov 20, 2018
@codecholeric codecholeric deleted the fix-assertionerror-mem-leak branch November 20, 2018 16:05
codecholeric added a commit that referenced this pull request Feb 21, 2021
Fixed memory leak in ArchRule.AssertionError in combination with JUnit 4
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant