Skip to content

Conversation

@ChrisPulman
Copy link
Member

@ChrisPulman ChrisPulman commented May 11, 2024

What kind of change does this PR introduce?

Fix for #659

What is the current behavior?

A memory leak exists in the ValidationContext

What is the new behavior?

ValidationContext has been updated to remove the leak
ReadOnlyCollectionPooled has been removed
ReadOnlyDisposableCollection has replaced ReadOnlyCollectionPooled

What might this PR break?

Disposing will clean the Resorces created

Please check if the PR fulfills these requirements

  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been added / updated (for bug fixes / features)

Other information:

@ChrisPulman
Copy link
Member Author

Looks like the ReadOnlyCollectionPooled is also not releasing, it runs fine on my PC, but not on the build server, I will take a look later.

Use ReadOnlyDisposableCollection
@ChrisPulman ChrisPulman enabled auto-merge (squash) May 11, 2024 08:04
@ChrisPulman ChrisPulman disabled auto-merge May 11, 2024 08:04
@ChrisPulman ChrisPulman merged commit 3834d5e into main May 11, 2024
@ChrisPulman ChrisPulman deleted the FixForMemoryLeak branch May 11, 2024 08:05
@github-actions
Copy link

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 26, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants