Cascading memory leak when StrokeShape is set on Border control on iOS

[AdamEssenmacher]

Description

Setting the StrokeShape property on a Border control in iOS results in the control and its containing page to leak.

Page-level leaks are serious, as they prevent child elements from being collected as well.

Steps to Reproduce

1. Push a page that contains a Border with its StrokeShape property set
2. Pop the page
3. Force GC runs
4. Observe the page is never collected

Link to public reproduction project repository

https://github.com/AdamEssenmacher/iOSBorderLeak.Maui

Version with bug

8.0.3

Is this a regression from previous behavior?

Not sure, did not test other versions

Last version that worked well

Unknown/Other

Affected platforms

iOS

Affected platform versions

iOS 17.2

Did you find any workaround?

No response

Relevant log output

No response

[AdamEssenmacher]

Would the area/perf label be appropriate here as well? This issue causes entire pages (and possibly nav stacks) not to be GC'ed, which causes noticeable performance degradation once the app starts needing swap space, and ultimately leading to forced app termination.

[jsuarezruiz]

Thanks for the details and the sample Adam. Cannot reproduce in main branch, could you try with the latest nightly package?

[jsuarezruiz]

Could have been fixed by #21151

[AdamEssenmacher]

@jsuarezruiz I just confirmed this appears to be fixed in 8.0.40-nightly.10455

[jonathanpeppers]

Thanks! Fix was:

• [ios] fix memory leak in RadioButton #21151