App leaks memory permanently

Feedback Case Number: 76017


I have filed the issue with a demo project and would appreciate if this case could be supported via thumbs up, so that the case gets a focus.

Probably someone can add some information if that project has similar results on windows too.

Best regards

i would run a method repeatedly with a timer in an interval and secondary output the runtime class status with object count and memory.

I wonder if this issue is related to this:

I noticed in the test code a comment that says “the leak doesn’t happen if you call it via a function call instead of inline”. This observation matches what we found in 75794, which is that objects created in a loop inside a function that go out of scope aren’t necessarily released from memory until the local scope ends (i.e., at the end of a method call).

1 Like