Memory leak when trying to read objects from the api at /v1/objects

[ciantfv456]

Describe the bug

We have a script that queries all of the services on icinga2 from the API. The memory usage keeps increasing every time we access the /v1/objects route on the API.

To Reproduce

Provide a link to a live example, or an unambiguous set of steps to reproduce this bug. Include configuration, logs, etc. to reproduce, if relevant.

1. Run icinga2 2.14 on container
2. Create 40000 services
3. Query the API at /v1/objects multiple times
4. See the memory increasing

Expected behavior

The memory that was allocated to the query should be set free after sending back the request

Your Environment

Include as many relevant details about the environment you experienced the problem in

• Version used (icinga2 --version): 2.14.0
• Operating System and version: container running on centos 7
• Enabled features (icinga2 feature list): icingadb api checker
• Icinga Web 2 version and modules (System - About): 2.14.1

[Jamess11]

Hey, it happend to me too. It seems like icinga2 doesn't free the memory allocated when querying the API for objects. When it queries a lot of objects periodically the memory usage keeps increasing until the vm gets oom kill