Bugzilla

Each call to `Bugzilla->active_custom_fields()` uses between 1600 to 1800 memory per call. This memory is not leaked -- it is returned when the request cache is cleaned up, but it grows to the number of bugs returned in the request.

Further investigation shows it isn't `active_custom_fields()` itself, but rather the hook that adds tracking flags.

Immediate-ish remediation for this would be bumping the max memory limit up a bit -- 3G instead of 2G may be sufficient.
Quick remediation would passing `skip_extensions` to `Bugzilla->active_custom_fields()` when `include_fields` doesn't include any tracking flags.

The most correction remediation would be making Tracking Flags extension not cache so aggressively.

Each call to `Bugzilla->active_custom_fields()` uses between 1600 kb to 1800 kb of memory per call. This memory is not leaked -- it is returned when the request cache is cleaned up, but it grows to the number of bugs returned in the request.

Further investigation shows it isn't `active_custom_fields()` itself, but rather the hook that adds tracking flags.

Immediate-ish remediation for this would be bumping the max memory limit up a bit -- 3G instead of 2G may be sufficient.
Quick remediation would passing `skip_extensions` to `Bugzilla->active_custom_fields()` when `include_fields` doesn't include any tracking flags.

The most correction remediation would be making Tracking Flags extension not cache so aggressively.