使用 DevPartner 的问题
我正在使用 DevPartner 来跟踪长时间运行的 .NET/WPF 应用程序中的内存泄漏。 DevPartner 告诉我哪些类随着时间的推移正在泄漏（主要是 WeakReference，但也包括 effectiveValueEntry 和 WeakDependencySource）。
我需要知道的是哪些其他对象仍然引用这些对象，以防止它们被垃圾收集。 DevPartner“查看 RAM 占用空间”报告（应用程序运行时）应该向我提供此信息...但该报告不会显示。
我在“内存分析”模式下运行该程序，我可以看到内存消耗最高或实例数最高的类列表。 “查看 RAM 占用空间”按钮已启用，但按下它似乎没有任何效果。
我想知道是否有其他人遇到过这个问题，或者是否有人对如何使报告再次工作有任何建议。
我尝试查看 MicroFocus 论坛，但它们似乎已关闭。
I'm using DevPartner to track down memory leaks in a long-running .NET/WPF app. DevPartner tells me what classes are being leaked over time (primarily WeakReference, but also EffectiveValueEntry and WeakDependencySource).
What I need to know is what other object(s) still have references to these in order to prevent them from being garbage-collected. The DevPartner "View RAM Footprint" report (while the app is running) SHOULD give me this information... but the report will not display.
I'm running the program under "Memory Analysis" mode, and I can see a list of classes with the highest memory consumption or highest instance count. The "View RAM Footprint" button is enabled, but pressing it appears to have no effect.
I was wondering if anybody else has encountered this issue or if anybody has any suggestions on how to get the report working again.
I tried to look at the MicroFocus forums, but they appear to be down.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
Jeff，您使用的是哪个版本的 DevPartner 和 Visual Studio？新的 Micro Focus 社区网站刚刚开放。那里尚未加载太多 DevPartner 内容，但如果您在那里发布问题详细信息，您可能会得到客户服务人员的回复。 DevPartner Studio 10.5 将于 2 月 4 日发布，因此请尝试获取该版本，以防您的问题在其中得到纠正。无耻插件：我密切参与 DevPartner 团队，因此我一直在寻找人们成功使用 DevPartner 的方法。
Jeff, what versions of DevPartner and Visual Studio are you using? The new Micro Focus community site just opened. There is not much DevPartner content loaded there yet, but if you post your issue details there you may get someone in customer care to respond. DevPartner Studio 10.5 ships on Feb. 4 so try to obtain that in case your issue is corrected in it. Shameless plug: I am intimately involved in the DevPartner team so I am always looking for ways folks use DevPartner successfully.