Home

.NET MAUI Performance Troubleshooting Index

This is the starting point for developers who want to improve the performance of their .NET MAUI applications. It includes focused guides that help you:

• Identify common problems in layout, async code, memory usage, and startup time
• Use profiling tools like dotnet-trace, PerfView, or VS Diagnostic Tools
• Interpret diagnostic output into actionable improvements
• Apply best practices based on guidance from the .NET MAUI and .NET performance communities

---

🧭 Guide Index

Topic	Description
quick-checklist	Common fixes and mistakes to catch before profiling
async-and-ui-thread	Validate async/await usage and prevent UI freezes
layout-performance	Find and fix slow or over-complex layouts
memory-leaks	Track down memory leaks using common patterns and tools
image-asset-optimization	Optimize image usage to reduce memory and improve rendering
startup-performance	Improve cold start performance and trim unnecessary work
profiling-guide	Capture and analyze traces with dotnet-trace, PerfView, or Speedscope
common-patterns-and-fixes	Fixes for frequently encountered issues

You can follow one guide at a time or work through them all. If you're not sure where to start, use the Quick Checklist.

---

💬 Copilot Chat Prompt

I've collected trace and memory data from my .NET MAUI app. Help me interpret the results and suggest fixes for common performance issues.

Run these checks for me:
1. Analyze async/await patterns (blocking calls, async void methods, UI thread work)
2. Audit layout complexity (excessive nesting, non-virtualized lists)
3. Identify memory leaks (event handler subscriptions, unmanaged resources)
4. Review image/resource usage
5. Check startup and build configurations

For each finding, categorize with:
✅ Optimized/no issue
❌ Critical issue
⚠️ Potential issue
ℹ️ Informational note

For each issue, provide code fixes and configuration suggestions.