Clear the Introspector caches in tests #41604
Merged
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.
The introspector cache keeps a reference to the class loader and it's one of the reasons for our class loader leaks.
Note that the calls to the Introspector are coming from REST Assured and especially from their Groovy machinery.
This actually makes a big difference when REST Assured is in use.
This is a typical heap dump when running
extensions/opentelemetry/deployment
tests before this patch:And after the patch: