Huge memory consumption in v2

[Axel29]

Preconditions (*)

1. Version 2.x

Steps to reproduce (*)

1. Instanciate a \Storyblok\Client object
2. Call the "resolveLinks" method with the "story" parameter passed to it
3. Call the "resolveRelations" method and add some relations to the client
4. Call the "getStoryByUuid" method to fetch a story by its UUID
5. Watch your RAM while the whole process is running

Expected result (*)

1. The query is made with no issue and the RAM isn't consumed more than it should

Actual result (*)

1. The RAM decreases until it is completely consumed by the process
2. The process gets killed

Explanation

The bug seems to have appeared in the commit #adb52f212e5f3ff38457ea4c7781a85f9f99e460 after adding the calls to the enrichStory method in the responseHandler method.

When I put a dump() in the enrichContent method, it parses way more data than when the resolveRelations method isn't called.

[joaokamun]

@Axel29 can you give me some more info? which php version, operating system, how many links and relations?

[Axel29]

@Axel29 can you give me some more info? which php version, operating system, how many links and relations?

Hello @joaokamun , I'm using PHP 7.4, on Docker (images from Magento Cloud Docker) thus on Linux, and only 2 relations added to the resolveRelations() method.

[roberto-butti]

Hey @Axel29 did you still have the issue with the latest version? After the commit you mentioned we refactored and improved the resolve relation mechanism under the hood.