Fix memory leak in CI config includes entry
1 unresolved thread
1 unresolved thread
Compare changes
Files
2- Grzegorz Bizon authored
In GitLab 11.9, gitlab-foss!24098 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 commit fixes this by doing away with the class variable in favor of `ComposableArray`. Changelog: fixed
@@ -7,7 +7,7 @@ module Entry
@@ -23,16 +23,8 @@ class Includes < ::Gitlab::Config::Entry::Node