Navigation Memory leak

ns-v8ios since version 7 I think have this issue. Where garbage collector is not operating as intended. I think there's a duplicate about this topic in the issue list, but it's easier to create one for myself with all necessary details.

So the leak is happening even on the app that you can install with ns create. If you create one using the template where this code exists

Frame.topmost().navigate({
    moduleName: componentRoute,
    transition: {
      name: 'fade',
    },
})

I've tried to modify it in a way to use util GC(). It helped, by a tiny bit, but it's still not enough. I've made a video where I profile hello world app on iPhone and show on screen what is happening on my device. I'm basically jumping between template heavy pages that have bunch of

<GridLayout class="page__content">
        <Label class="page__content-icon far" text="&#xf1ea;"></Label>
        <Label class="page__content-placeholder" text="<!-- Page content goes here -->"></Label>
</GridLayout>

duplicated. On one page 300 lines, on the second one 6000 lines. And it's clearly visible that memory is being released by accumulates much much more.
Why so much lines is just to display that GC is clearly broken, but even in live app that I have, I have "complex" layouts because we're using NS-Vue and components approach create a lot of templates, even if they are flat. So our app crashing our clients devices quite easily, especially the ones that have only 2-3GB of RAM and the solution to make design more flat might not be a solution for us at all, unfortunately.

Version of xcode: 13.1
Version of ns-cli: 8.1.4
Version of ns-core: 8.1.1
Version of ios-runetime: 8.1.0

We would like to "invest" into this problem, to fix it ASAP, as our product suffers from this.

Here's there link to a video where I show the error https://drive.google.com/file/d/1Qz8jYFE6N4TVvS0G_8rrvmVzUe-KtKFC/view?usp=sharing

Beginne damit, das Problem in einer mit dem ns create template erstellten App zu reproduzieren, und verwende dabei das Frame.topmost().navigate-Beispiel sowie die aufgeführten Versionen von iOS, ns-cli, ns-core und ios-runtime. Profiliere die Navigation zwischen den beschriebenen Seiten auf einem iPhone und vergleiche das Speicherverhalten mit und ohne die versuchte GC()-Änderung. Als erledigt gilt die Aufgabe, wenn der Navigations-Leak behoben ist und sich der Speicher nicht mehr anhäuft, bis die App abstürzt.