The JetBrains Blog

Deprecating dotMemory Unit

7.5内容质量
Deprecating dotMemory Unit

TL;DR · AI 摘要

JetBrains 宣布弃用 dotMemory Unit,建议用户迁移到其他内存测试工具。

核心要点

  • dotMemory Unit 将于 2026 年底正式停止支持。
  • 推荐使用 dotMemory 或其他第三方工具进行内存泄漏测试。
  • JetBrains 提供迁移指南以帮助用户过渡到新工具。

结构提纲

按章节快速跳转。

  1. JetBrains 决定停止支持 dotMemory Unit,专注于其他工具。

  2. dotMemory Unit 使用率下降,维护成本较高。

  3. 推荐使用 dotMemory 或其他第三方工具进行内存测试。

  4. JetBrains 提供详细文档帮助用户迁移到新工具。

思维导图

用一张图看清主题之间的关系。

查看大纲文本(无障碍 / 无 JS 友好)
  • Deprecating dotMemory Unit

金句 / Highlights

值得收藏与分享的关键句。

#JetBrains#dotMemory#内存测试#.NET
打开原文

Deprecating dotMemory Unit | The .NET Tools Blog

[](https://blog.jetbrains.com/dotnet/2026/05/28/deprecating-dotmemory-unit/#)

Cookie Settings

Our website uses some cookies and records your IP address for the purposes of accessibility, security, and managing your access to the telecommunication network. You can disable data collection and cookies by changing your browser settings, but it may affect how this website functions. Learn more

With your consent, JetBrains may also use cookies and your IP address to collect individual statistics and provide you with personalized offers and ads subject to the Privacy Notice and the Terms of Use. JetBrains may use third-party services for this purpose. You can adjust or withdraw your consent at any time by visiting the Opt-Out.

Accept All Manage Settings

[![Image 2](https://blog.jetbrains.com/wp-content/uploads/2024/06/JETBRAINS-Blog.svg)](https://blog.jetbrains.com/)Skip to content

Burger menu icon

  • #### IDEs
  • [CLion](https://blog.jetbrains.com/clion/ "CLion Blog")
  • [DataGrip](https://blog.jetbrains.com/datagrip/ "DataGrip Blog")
  • DataSpell
  • [GoLand](https://blog.jetbrains.com/go/ "GoLand Blog")
  • [IntelliJ IDEA](https://blog.jetbrains.com/idea/ "IntelliJ IDEA Blog")
  • [PhpStorm](https://blog.jetbrains.com/phpstorm/ "PhpStorm Blog")
  • [PyCharm](https://blog.jetbrains.com/pycharm/ "PyCharm Blog")
  • RustRover
  • [Rider](https://blog.jetbrains.com/dotnet/tag/rider/ "Rider Blog")
  • [RubyMine](https://blog.jetbrains.com/ruby/ "RubyMine Blog")
  • [WebStorm](https://blog.jetbrains.com/webstorm/ "WebStorm Blog")
  • #### Plugins & Services
  • #### Team Tools
  • #### .NET & Visual Studio
  • [.NET Tools](https://blog.jetbrains.com/dotnet/ ".NET Tools")
  • [ReSharper C++](https://blog.jetbrains.com/rscpp/ "ReSharper C++ Blog")
  • #### Languages & Frameworks
  • [Kotlin](https://blog.jetbrains.com/kotlin/ "Kotlin Blog")
  • Ktor
  • [MPS](https://blog.jetbrains.com/mps/ "MPS Blog")
  • Amper
  • #### Education & Research
  • #### Company

![Image 3: Dotnet logo ## .NET Tools](https://blog.jetbrains.com/dotnet/) Essential productivity kit for .NET and game developers

Follow

Get Tools

.NET ToolsdotMemory

Deprecating dotMemory Unit

Image 4: Alexander Kurakin
Image 4: Alexander Kurakin

Alexander Kurakin

May 28, 2026

dotMemory Unit has long served as a unit testing framework for detecting memory issues in .NET code. We are grateful to everyone who has used it as part of their development and testing workflows.

After careful consideration, we have decided to retire dotMemory Unit. The project will no longer receive active maintenance, compatibility updates, or security fixes, and we recommend that users plan to discontinue its use.

Why we’re making this change Copy heading link

This decision is based on several technical, security, and product considerations.

dotMemory Unit has not been actively developed for some time and does not support the latest .NET versions. Bringing it up to modern compatibility, reliability, and security standards would require a substantial architectural redesign.

In addition, dotMemory Unit generates workspaces in a legacy format that is incompatible with recent versions of dotMemory. This creates friction for users and prevents seamless integration with the latest JetBrains profiling tools.

Finally, some of the project’s dependencies are outdated and include known security vulnerabilities. Because dotMemory Unit is no longer actively maintained, we cannot reliably update these dependencies without risking compatibility issues or undertaking a full rebuild. Continuing to distribute or support tooling with unpatched vulnerabilities would not meet our security standards.

What this means for you Copy heading link

If you currently use dotMemory Unit, we strongly recommend that you stop using it, especially in security-sensitive environments.

We understand that dotMemory Unit has been valuable for in-test memory profiling, and we recognize that its deprecation may create a gap in some workflows. At this time, we do not have a direct replacement.

Timeline Copy heading link

[20.05.2026]: dotMemory Unit marked as deprecated on NuGet.org. No further updates, patches, or security fixes will be released.

[28.05.2026]: Official deprecation notice posted across different channels.Documentation will remain online for some time, but will be updated to reflect the current state of the project and potential risks.

Thank you Copy heading link

We are sincerely grateful to everyone who has trusted dotMemory Unit over the years.

DeprecateddotMemory Unit

_Prev post_ What Happens When You Give AI Agents the Map of Your Code’s Coverage?