Description

A memory leak occurs when an implicit style with an associated trigger is used.

Please see the linked repository for a reproduction, where I have created a rudimentary test harness to illustrate the issue.

Steps to Reproduce

1. Run the sample at the linked repository
2. Use the navigate button to navigate to a new page, and press the back arrow to go back to the original page. Repeat this a number of times.
3. Back on the main page, use the GC button to trigger garbage collections by clicking a few times.
4. Observe the memory usage does not return to baseline.
5. Remove the style from the App constructor and repeat the steps above
6. Observe the memory returns to baseline

Above: Image with style present

Above: Image with style removed

Link to public reproduction project repository

https://github.com/markmccaigue/mauitriggerleaktest

Version with bug

8.0.20 SR4

Is this a regression from previous behavior?

Not sure, did not test other versions

Last version that worked well

Unknown/Other

Affected platforms

iOS, Android, I was not able test on other platforms

Affected platform versions

No response

Did you find any workaround?

No response

Relevant log output

No response