{"id":54183,"date":"2025-11-25T16:33:46","date_gmt":"2025-11-25T16:33:46","guid":{"rendered":"https:\/\/www.devopsschool.com\/blog\/?p=54183"},"modified":"2026-02-21T08:29:08","modified_gmt":"2026-02-21T08:29:08","slug":"dotmemory-a-complete-tutorial-guide","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/blog\/dotmemory-a-complete-tutorial-guide\/","title":{"rendered":"dotMemory: A Complete Tutorial Guide dotMemory console command line tool"},"content":{"rendered":"\n
\"\"<\/figure>\n\n\n\n
\n\n\n\n
\n\n\n\n
\"\"<\/figure>\n\n\n\n

<\/p>\n\n\n\n

\n\n\n\n

A Complete Practical Guide for Memory Profiling Using Command Line<\/em><\/h3>\n\n\n\n
\n\n\n\n

1. \ud83d\udd0d What is dotMemory Console?<\/strong><\/h1>\n\n\n\n

dotMemory Console<\/strong> (also called dotMemory Command-Line Profiler<\/strong>) is the free<\/strong>, headless version of JetBrains dotMemory that allows you to:<\/p>\n\n\n\n

    \n
  • Start .NET processes under memory profiling<\/li>\n\n\n\n
  • Attach to a running .NET process<\/li>\n\n\n\n
  • Automatically capture memory snapshots<\/strong><\/li>\n\n\n\n
  • Trigger snapshots based on conditions (timer, memory growth, process start)<\/li>\n\n\n\n
  • Profile desktop apps, web apps, Windows services, IIS, WCF services<\/li>\n\n\n\n
  • Capture snapshots on servers, CI pipelines, or production-like environments<\/li>\n<\/ul>\n\n\n\n

    The console profiler produces snapshot (.dmw)<\/strong> files that can later be opened in the dotMemory GUI<\/strong> (paid), but everything up to taking snapshots is 100% free<\/strong>.<\/p>\n\n\n\n

    \n\n\n\n

    2. \ud83c\udfaf Why Use dotMemory Console?<\/strong><\/h1>\n\n\n\n

    Because GUI profilers cannot run<\/strong> in many real scenarios.<\/h3>\n\n\n\n

    dotMemory Console is perfect for:<\/h3>\n\n\n\n

    \u2714 Profiling on servers<\/strong>
    \u2714 Profiling CI\/CD pipelines<\/strong>
    \u2714 Profiling performance test environments<\/strong>
    \u2714 Profiling apps running under service accounts<\/strong>
    \u2714 Profiling IIS, Kestrel, Windows services<\/strong>
    \u2714 Capturing snapshots automatically<\/strong> during load tests
    \u2714 Capturing leaks in production-like staging<\/strong><\/p>\n\n\n\n

    In short:<\/p>\n\n\n\n

    \n

    You use dotMemory Console when you need real-world profiling without installing heavy GUI tools.<\/strong><\/p>\n<\/blockquote>\n\n\n\n

    \n\n\n\n

    3. \ud83e\udde0 Why Memory Profiling Matters<\/strong><\/h1>\n\n\n\n

    Memory issues cause:<\/p>\n\n\n\n

      \n
    • High GC (Garbage Collection) \u2192 CPU spikes<\/li>\n\n\n\n
    • Slow response times<\/li>\n\n\n\n
    • Server crashes<\/li>\n\n\n\n
    • Out-of-memory exceptions<\/li>\n\n\n\n
    • Leaks (objects never collected)<\/li>\n\n\n\n
    • Long-lived objects blocking GC<\/li>\n\n\n\n
    • LOH (Large Object Heap) fragmentation<\/li>\n<\/ul>\n\n\n\n

      dotMemory Console helps you capture snapshots at the EXACT moment the issue happens<\/strong>, which is not possible with GUI tools.<\/p>\n\n\n\n

      \n\n\n\n

      4. \ud83e\udded Where dotMemory Console Can Be Used<\/strong><\/h1>\n\n\n\n
      Environment<\/th>Supported?<\/th><\/tr><\/thead>
      Windows Desktop<\/td>\u2714<\/td><\/tr>
      Windows Server<\/td>\u2714<\/td><\/tr>
      Linux (.NET Core)<\/td>\u2714<\/td><\/tr>
      macOS (.NET Core)<\/td>\u2714<\/td><\/tr>
      Docker<\/td>\u2714<\/td><\/tr>
      Remote servers<\/td>\u2714<\/td><\/tr>
      CI pipelines<\/td>\u2714<\/td><\/tr>
      IIS \/ IIS Express<\/td>\u2714<\/td><\/tr>
      Windows Services<\/td>\u2714<\/td><\/tr>
      Console apps<\/td>\u2714<\/td><\/tr>
      ASP.NET Core apps (Kestrel)<\/td>\u2714<\/td><\/tr>
      Worker Services<\/td>\u2714<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
      \n\n\n\n

      5. \ud83c\udfd7 How dotMemory Console Works (Internals)<\/strong><\/h1>\n\n\n\n
        \n
      1. You start profiling using commands like:\n
          \n
        • dotMemory start<\/code><\/li>\n\n\n\n
        • dotMemory get-snapshot<\/code><\/li>\n<\/ul>\n<\/li>\n\n\n\n
        • The profiler injects into the CLR runtime.<\/li>\n\n\n\n
        • It records allocation stacks, object references, and GC behavior.<\/li>\n\n\n\n
        • When a snapshot is triggered:\n
            \n
          • It dumps the entire managed heap.<\/li>\n\n\n\n
          • It saves it into a .dmw<\/code> workspace file.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
          • You later open .dmw<\/code> in GUI (optional) to see:\n
              \n
            • Objects<\/li>\n\n\n\n
            • Leaks<\/li>\n\n\n\n
            • GC roots<\/li>\n\n\n\n
            • Retained memory<\/li>\n\n\n\n
            • Allocation hot paths<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n\n\n\n
              \n\n\n\n

              6. \ud83d\udce6 Installation (FREE)<\/strong><\/h1>\n\n\n\n

              Option 1: Global Install (Recommended)<\/strong><\/h2>\n\n\n
              dotnet<\/span> tool<\/span> install<\/span> --global<\/span> JetBrains<\/span>.dotMemory<\/span>.Console<\/span>\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
              Check version:<\/p>\n\n\n
              dotmemory --version\n<\/code><\/span><\/pre>\n\n\n
              \n\n\n\n
              Option 2: Local Install (Project-based CI)<\/strong><\/h2>\n\n\n
              dotnet<\/span> new<\/span> tool-manifest<\/span>\ndotnet<\/span> tool<\/span> install<\/span> JetBrains<\/span>.dotMemory<\/span>.Console<\/span>\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
              \n\n\n\n
              Option 3: Manual Download ZIP<\/strong><\/h2>\n\n\n\n
              Download from JetBrains (no account needed):
              Search \u201cJetBrains dotMemory Console download\u201d<\/strong><\/p>\n\n\n\n
              Extract to:<\/p>\n\n\n
              C<\/span>:toolsdotmemory<\/span>\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
              Run:<\/p>\n\n\n
              dotMemory<\/span>.exe<\/span>\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
              \n\n\n\n
              7. \ud83e\uddf0 Features of dotMemory Console (FREE)<\/strong><\/h1>\n\n\n\n
              \u2714 Attach to running processes
              \u2714 Profile apps as they start
              \u2714 Support for .NET Framework and .NET Core
              \u2714 Automatic triggers
              \u2714 No GUI needed
              \u2714 Zero license cost
              \u2714 Works on servers
              \u2714 Snapshot packaging
              \u2714 Works with IIS \/ Kiestrel \/ Windows Services
              \u2714 Suitable for CI\/CD
              \u2714 Very low overhead<\/p>\n\n\n\n
              \n\n\n\n
              8. \u26a1 Advantages<\/strong><\/h1>\n\n\n\n
              Advantage<\/th>Explanation<\/th><\/tr><\/thead>
              \u2714 Free<\/td>The full command-line profiler is FREE<\/td><\/tr>
              \u2714 Works on Servers<\/td>No need to install big GUI tools<\/td><\/tr>
              \u2714 Automation<\/td>Perfect for CI, load tests<\/td><\/tr>
              \u2714 No IDE dependency<\/td>Works with any environment<\/td><\/tr>
              \u2714 Supports all .NET apps<\/td>Desktop, web, service<\/td><\/tr>
              \u2714 Trigger-based profiling<\/td>Catch leaks automatically<\/td><\/tr>
              \u2714 Lightweight<\/td>Low overhead vs GUI<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
              \n\n\n\n
              9. \u26a0 Limitations<\/strong><\/h1>\n\n\n\n
              Limitation<\/th>Explanation<\/th><\/tr><\/thead>
              \u274c No visual interface<\/td>Must open snapshots in GUI (paid)<\/td><\/tr>
              \u274c Cannot analyze snapshots in CLI<\/td>You only collect snapshots<\/td><\/tr>
              \u274c No real-time object graph<\/td>GUI required to view<\/td><\/tr>
              \u274c Not ideal for beginners<\/td>Requires understanding of profiling<\/td><\/tr>
              \u274c Some runtime-specific features require GUI<\/td>E.g., graph-based navigation<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
              \n\n\n\n
              10. \ud83d\ude80 How To Use dotMemory Console (Hands-On)<\/strong><\/h1>\n\n\n\n
              \n\n\n\n
              \u2714 10.1 Take Snapshot of Running Process<\/strong><\/h1>\n\n\n\n
              By process name:<\/h3>\n\n\n
              dotMemory get<\/span>-snapshot MyApp.exe --save-to-dir=C:snaps\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
              By PID:<\/h3>\n\n\n
              dotMemory get<\/span>-snapshot 12564 --save-to-dir=C:snaps\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
              dotMemory chooses highest-memory instance<\/strong> if multiple processes exist.<\/p>\n\n\n\n
              \n\n\n\n
              \u2714 10.2 Start App Under Profiling<\/strong><\/h1>\n\n\n
              dotMemory start --save-to-dir=C:snaps C:MyAppMyApp.exe\n<\/code><\/span><\/pre>\n\n\n
              While app runs, you can manually trigger snapshot:<\/p>\n\n\n
              get<\/span>-snapshot\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
              OR:<\/p>\n\n\n
              Ctrl + Enter\n<\/code><\/span><\/pre>\n\n\n
              \n\n\n\n
              \u2714 10.3 Start .NET Core App (Kestrel)<\/strong><\/h1>\n\n\n
              dotMemory start-net-core --save-to-dir=C:snaps -- MyApp.dll\n<\/code><\/span><\/pre>\n\n\n
              \n\n\n\n
              \u2714 10.4 Automatic Snapshots (Memory Increase Trigger)<\/strong><\/h1>\n\n\n\n
              Example: snapshot when memory increases by 40%<\/h3>\n\n\n
              dotMemory start --trigger-mem-inc=40% --save-to-dir=C:snaps MyApp.exe\n<\/code><\/span><\/pre>\n\n\n
              Perfect for:<\/p>\n\n\n\n
              \u2714 Memory leaks
              \u2714 Load-test environments<\/p>\n\n\n\n
              \n\n\n\n
              \u2714 10.5 Snapshots Every X Seconds<\/strong><\/h1>\n\n\n\n
              Every 30 seconds:<\/h3>\n\n\n
              dotMemory start --trigger-timer=30s --save-to-dir=C:snaps MyApp.exe\n<\/code><\/span><\/pre>\n\n\n
              \n\n\n\n
              \u2714 10.6 At App Startup<\/strong><\/h1>\n\n\n
              dotMemory start --trigger-start --save-to-dir=C:snaps MyApp.exe\n<\/code><\/span><\/pre>\n\n\n
              \n\n\n\n
              \u2714 10.7 Profile IIS<\/strong><\/h1>\n\n\n\n
              Restart IIS under profiler:<\/h3>\n\n\n
              dotMemory start-iis --save-to-dir=C:snaps\n<\/code><\/span><\/pre>\n\n\n
              Attach:<\/h3>\n\n\n
              dotMemory get<\/span>-snapshot w3wp --save-to-dir=C:snaps\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
              \n\n\n\n
              \u2714 10.8 Profile Windows Service<\/strong><\/h1>\n\n\n\n
              Start profiling:<\/p>\n\n\n
              dotMemory start-windows-service MyServiceName --save-to-dir=C:snaps\n<\/code><\/span><\/pre>\n\n\n
              Take snapshot:<\/p>\n\n\n
              dotMemory get<\/span>-snapshot MyServiceName --save-to-dir=C:snaps\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
              \n\n\n\n
              \u2714 10.9 Profile Any Process Started Later<\/strong><\/h1>\n\n\n\n
              Use this for \u201ccapture everything that starts now\u201d:<\/p>\n\n\n
              dotMemory profile-new<\/span>-processes --save-to-dir=C:snaps\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
              \n\n\n\n
              11. \ud83d\udcca What To See Inside Snapshots (When Opened in GUI)<\/strong><\/h1>\n\n\n\n
              Once you import .dmw<\/code> file into dotMemory GUI, analyze:<\/h3>\n\n\n\n
                \n
              1. Overview Page<\/strong>\n
                  \n
                • Total objects<\/li>\n\n\n\n
                • Object count growth<\/li>\n\n\n\n
                • Retained memory<\/li>\n<\/ul>\n<\/li>\n\n\n\n
                • Inspections<\/strong>\n
                    \n
                  • Potential leaks<\/li>\n\n\n\n
                  • Types that increase<\/li>\n\n\n\n
                  • Long-lived objects<\/li>\n<\/ul>\n<\/li>\n\n\n\n
                  • Object Sets<\/strong>\n
                      \n
                    • Group by type<\/li>\n\n\n\n
                    • Size and count per type<\/li>\n<\/ul>\n<\/li>\n\n\n\n
                    • Retention Paths<\/strong>\n
                        \n
                      • Why object is not collected<\/li>\n\n\n\n
                      • GC roots<\/li>\n<\/ul>\n<\/li>\n\n\n\n
                      • Allocations<\/strong>\n
                          \n
                        • Methods causing heavy memory traffic<\/li>\n<\/ul>\n<\/li>\n\n\n\n
                        • Compare Snapshots<\/strong>\n
                            \n
                          • Before & after requests<\/li>\n\n\n\n
                          • Leak tracking<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n\n\n\n
                            \n\n\n\n
                            12. \ud83e\uddea Real Use Cases<\/strong><\/h1>\n\n\n\n
                            \n\n\n\n
                            \u2714 12.1 Detect Memory Leak in ASP.NET Core Under Load<\/h2>\n\n\n\n
                            Run:<\/p>\n\n\n
                            dotMemory start --trigger-mem-inc=20% --save-to-dir=C:snaps -- dotnet MyApp.dll\n<\/code><\/span><\/pre>\n\n\n
                            Start JMeter \/ k6 load test
                            \u2192 Snapshots collected \u2192 Analyze retained size differences.<\/p>\n\n\n\n
                            \n\n\n\n
                            \u2714 12.2 Catch Leak in Windows Service<\/h2>\n\n\n
                            dotMemory get<\/span>-snapshot MyServiceName --save-to-dir=C:snaps\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                            Restart service \u2192 reproduce issue \u2192 compare snapshots.<\/p>\n\n\n\n
                            \n\n\n\n
                            \u2714 12.3 CI\/CD Pipeline Memory Regression Check<\/h2>\n\n\n\n
                            In Jenkins\/GitHub Actions:<\/p>\n\n\n
                            dotMemory start-net-core --trigger-mem-inc=30% --save-to-dir=snaps -- MyApp.dll\n<\/code><\/span><\/pre>\n\n\n
                            Upload snaps to artifacts.<\/p>\n\n\n\n
                            \n\n\n\n
                            \u2714 12.4 Taking a Snapshot Right Before Crash<\/h2>\n\n\n\n
                            Use trigger:<\/p>\n\n\n
                            dotMemory start --trigger-mem-inc=80% --save-to-dir=C:snaps MyApp.exe\n<\/code><\/span><\/pre>\n\n\n
                            If memory shoots up (OOM), you get snapshot automatically.<\/p>\n\n\n\n
                            \n\n\n\n
                            \u2714 12.5 Auto Snapshots Every X Minutes During Long-Running Tests<\/h2>\n\n\n
                            dotMemory start --trigger-timer=120s --save-to-dir=C:snaps MyApp.exe\n<\/code><\/span><\/pre>\n\n\n
                            \n\n\n\n
                            13. \ud83d\udcc1 Snapshot Storage and Recovery<\/strong><\/h1>\n\n\n\n
                            Save snapshots:<\/h3>\n\n\n
                            --save-to-dir=C:snaps\n<\/code><\/span><\/pre>\n\n\n
                            If profiling crashed:<\/h3>\n\n\n
                            dotMemory<\/span> recover<\/span> C<\/span>:snaps<\/span>\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
                            \n\n\n\n
                            14. \ud83e\uddfe Important Commands Cheat Sheet<\/strong><\/h1>\n\n\n\n
                            Purpose<\/th>Command<\/th><\/tr><\/thead>
                            Start app under profiling<\/td>start<\/code><\/td><\/tr>
                            Start .NET Core app<\/td>start-net-core<\/code><\/td><\/tr>
                            Attach to process<\/td>get-snapshot <PID><\/code><\/td><\/tr>
                            Auto snapshot on memory growth<\/td>--trigger-mem-inc=30%<\/code><\/td><\/tr>
                            Auto snapshot every X seconds<\/td>--trigger-timer=20s<\/code><\/td><\/tr>
                            Profile IIS<\/td>start-iis<\/code><\/td><\/tr>
                            Profile Windows Service<\/td>start-windows-service<\/code><\/td><\/tr>
                            Profile processes started later<\/td>profile-new-processes<\/code><\/td><\/tr>
                            Save snapshots<\/td>--save-to-dir=snaps<\/code><\/td><\/tr>
                            Recover workspace<\/td>recover<\/code><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
                            \n\n\n\n
                            15. \ud83c\udfaf Best Practices for Performance Engineers<\/strong><\/h1>\n\n\n\n
                            \u2714 Always save snapshots to a separate folder<\/h3>\n\n\n\n
                            \u2714 Take a baseline snapshot<\/h3>\n\n\n\n
                            \u2714 Take snapshot after load scenario<\/h3>\n\n\n\n
                            \u2714 Always compare snapshots<\/h3>\n\n\n\n
                            \u2714 Use memory-increase triggers for leaks<\/h3>\n\n\n\n
                            \u2714 Do not profile production unless necessary<\/h3>\n\n\n\n
                            \u2714 Automate snapshot collection in CI\/CD<\/h3>\n\n\n\n
                            \u2714 Keep snapshots small by recording at correct moments<\/h3>\n\n\n\n
                            \u2714 Use GUI only for deep analysis<\/h3>\n\n\n\n
                            \n\n\n\n
                            \ud83c\udf89 FINAL SUMMARY<\/strong><\/h1>\n\n\n\n
                            dotMemory Console = Free, powerful, server-ready memory profiler for .NET<\/strong>
                            It gives you:<\/p>\n\n\n\n
                              \n
                            • Automatic snapshots<\/li>\n\n\n\n
                            • Profiling of server apps<\/li>\n\n\n\n
                            • Integration with performance testing<\/li>\n\n\n\n
                            • 100% automation via command line<\/li>\n\n\n\n
                            • Ability to capture leaks exactly when they happen<\/li>\n\n\n\n
                            • No need for GUI installation<\/li>\n<\/ul>\n\n\n\n
                              To analyze snapshots \u2192 you need dotMemory GUI (paid), but all profiling and snapshot generation is free.<\/strong><\/p>\n\n\n\n
                              \n\n\n\n
                              <\/p>\n","protected":false},"excerpt":{"rendered":"
                              A Complete Practical Guide for Memory Profiling Using Command Line 1. \ud83d\udd0d What is dotMemory Console? dotMemory Console (also called dotMemory Command-Line Profiler) is the free, headless version of JetBrains… <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"_joinchat":[],"footnotes":""},"categories":[11138],"tags":[],"class_list":["post-54183","post","type-post","status-publish","format-standard","hentry","category-best-tools"],"_links":{"self":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/54183","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/comments?post=54183"}],"version-history":[{"count":4,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/54183\/revisions"}],"predecessor-version":[{"id":59885,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/54183\/revisions\/59885"}],"wp:attachment":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/media?parent=54183"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/categories?post=54183"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/tags?post=54183"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}