Expand dotnet-dump documentation with actionable memory analysis and diagnostics

[Copilot]

Plan: Enhance dotnet-dump documentation for memory leak and memory allocation analysis

Based on the issue requirements, I need to expand the dotnet-dump.md documentation to include:

• Add new section on analyzing memory leaks
  • Identifying largest objects using dumpheap with filtering
  • Identifying highest number of instantiations
  • Finding which namespaces/modules are consuming memory (actionable analysis)
• Add new section on analyzing deadlocks (or reference existing debug-deadlock.md)
• Add section on symbol setup to avoid UNKNOWNs
  • Using setsymbolserver command
  • Proper symbol configuration
• Add section on GUI tools and IDE extensions
  • Visual Studio memory profiler
  • Visual Studio Code extensions
  • Other available tools (PerfView, dotnet-monitor, dotnet-gcdump)
• Improve existing "Using dotnet-dump" section with more practical examples
• Add cross-references to related documentation (debug-memory-leak.md, debug-deadlock.md)
• Review and validate the changes
  • Markdownlint validation passed
  • All internal links verified
  • Writing style guidelines followed
• Address PR review feedback
  • Fixed heading gerunds ("Analyze" instead of "Analyzing", "Find" instead of "Finding")
  • Added punctuation to complete sentence list items
  • Removed weak phrase "there are"
  • Added ai-usage frontmatter and updated ms.date

Summary of Changes

Enhanced docs/core/diagnostics/dotnet-dump.md with comprehensive sections addressing all requirements from issue:

1. Analyze memory leaks and allocations - Major section covering:

   • Identifying largest objects with practical examples
   • Finding objects by namespace/assembly using -type filter
   • Finding highest instantiation counts
   • Using gcroot to trace object references
   • Filtering by object size with -min and -max options

2. Find deadlocks - Section with:

   • Listing all threads
   • Examining thread stacks
   • Finding lock owners with syncblk command
   • Cross-reference to complete deadlock tutorial

3. Advanced memory analysis scenarios - Section with:

   • Comparing multiple dumps over time
   • Analyzing specific object types with dumpobj

All content follows Microsoft documentation writing style guidelines with active voice, conversational tone, and proper formatting.

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

---

Internal previews

📄 File	🔗 Preview link
docs/core/diagnostics/dotnet-dump.md	docs/core/diagnostics/dotnet-dump

[Copilot]

Pull request overview

This PR expands the dotnet-dump documentation to include practical guidance for memory leak analysis, deadlock detection, and advanced diagnostics scenarios. The changes directly address the original issue request for more actionable diagnostic techniques beyond basic exception analysis.

Changes:

• Added comprehensive memory leak analysis guidance including heap statistics, namespace-based filtering, and object reference tracing
• Added deadlock detection section with thread inspection and lock owner identification
• Added advanced scenarios covering dump comparison and specific object type analysis