Jonathan Peppers

@ESO-ST `dotnet-gcdump` should work fine in combination with `dotnet-dsrouter`. If your app runs on MacCatalyst, you can also skip using `dotnet-dsrouter`. The iOS docs are here: * https://github.com/xamarin/xamarin-macios/wiki/Profiling But the...

The `dotnet-gcdump` command should be identical to `dotnet-trace`, and should work. One thing to check is if all the tools have the same version number. Do you get an error...

Ok, I've been using `-p {PID of dsrouter}` instead of `--diagnostic-port`. The Android instructions describe this workflow a bit.

Here are my steps to use `dotnet-gcdump`, they are not intuitive. I would expect folks to have trouble! First, I build a `Release` build of the app with `-p:_BundlerDebug=true`: ```sh...

@ivanpovazan we have an issue listing all the NativeAOT TODOs, I linked to this PR: * https://github.com/dotnet/android/issues/8724

After deeper investigation, I don't think I'm seeing a problem here on Windows. First, I would recommend these changes in the sample to test this: * https://github.com/krdmllr/MauiMemoryLeaks/compare/master...jonathanpeppers:RadioButtonLeaks:peppers The sample was...

The main thing to check is that an event fires once, instead of `ObservableCollection.CollectionChanged` firing 1-per item. In my example, it was actually `OnPropertyChanged(nameof(Items))` that refreshed the screen.

If you are always seeing 80, it's probably not a leak. It just means that it takes a few GCs for them to go away. A leak would mean 80->100->120...

For me, it was going down (lower than a previous collection) as I waited longer & clicked longer. There was a stable point the memory usage would hover around. If...

The `monodroid-assembly` log messages are not on by default. Did you run a command like this to enable them? ``` adb shell setprop debug.mono.log assembly ``` Simply enabling log messages...