Fix memory leak in CI config includes entry
1 unresolved thread
1 unresolved thread
Compare changes
Files
2@@ -7,7 +7,7 @@ module Entry
@@ -23,16 +23,8 @@ class Includes < ::Gitlab::Config::Entry::Node
This backports !122462 (merged) to 15-10-stable-ee
.
In GitLab 11.9, gitlab-foss!24098 (merged)
introduced validation of include
keywords. However, it quietly
introduced a memory leak: any time a new include
entry was
instantiated, a proc would be added to the aspects
class variable.
As the list grew, the time taken to process other include
keywords
would grow.
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
e2e:package-and-test-ee
job has either succeeded or been approved by a Software Engineer in Test.If you have questions about the patch release process, please:
#releases
Slack channel (internal only).