blocks|key|67020|text|要查找内存泄漏，您可以尝试使用Visual+Leak+Detection工具。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|67021|entityMap|0|LINK|mutability|MUTABLE|url|http://vld.codeplex.com/^0|F|L|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

For finding memory leaks you can try <a href="http://vld.codeplex.com/" rel="nofollow noreferrer">Visual Leak Detection</a> tool.

blocks|key|4828653|text|正如Ori提到的那样，Micro的DevPartner工作室具有泄漏检测和其他运行时分析功能。与Compuware下DPS的高昂价格不同，如果需要的话，您现在可以只许可运行时分析器，而不是整个套件。不知羞耻的插头:我在DevPartner团队工作。我们的64位应用程序支持将于2011年2月4日发布10.5版本。在http://www.DevPartner.com上查找发布新闻和评估下载。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|4828654|entityMap|0|LINK|mutability|MUTABLE|url|http://www.devpartner.com/^0|4D|P|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

Noah, as Ori mentioned, DevPartner Studio from Micro Focus has both leak detection and other runtime profiling features. Unlike the lofty prices DPS had under Compuware, you can now license just the runtime profilers and not the whole suite if that's what you need. Shameless plug: I work on the DevPartner team. Our 64-bit application support ships in the 10.5 release on February 4, 2011. Look for release news and eval downloads on <a href="http://www.DevPartner.com" rel="nofollow">http://www.DevPartner.com</a>.

blocks|key|2715757|text|就我个人而言，我喜欢DevPartner。如果你在一家大公司工作，也许你可以说服他们支付高额的许可证。它很贵，但它非常非常结实。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2715758|entityMap|0|LINK|mutability|MUTABLE|url|http://en.wikipedia.org/wiki/DevPartner^0|A|A|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

Personally, I'm fond of <a href="http://en.wikipedia.org/wiki/DevPartner" rel="nofollow noreferrer">DevPartner</a>. If you work in a big company, maybe you can convince them to pay for the hefty license. It's expensive, but it's very very sturdy.

blocks|key|66996|text|我使用了几个商业替代方案，虽然它们可以提供奇妙的结果，但由于未知的原因，它们也经常无法工作：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|66997|66998|Rational+Quantity:性能分析的奇妙产品，但是他们在几年中没有发布新的版本，并且经常(在我的例子中)软件经常拒绝工作|unordered-list-item|66999|AQTime:也非常好(少于Rational+Quantity)，但有时也拒绝为未知的reasons.|67000|Performance验证器工作:same|67001|AQTime|67002|67003|在过去的几年里，我又回到了对应用程序进行采样的相当粗糙的方式上。这不像使用插装那么完美，但它要快得多，可以在任何应用程序上运行，并且始终有效。我最喜欢的是"Very+Sleepy“(http://www.codersnotes.com/sleepy)，但Luke+StackWalker+(http://lukestackwalker.sourceforge.net/)也很不错。因为应用程序可以立即运行，并且没有明显的减速，所以“更改应用程序，配置文件”循环非常简短和高效。|offset|length|67004|要查找内存泄漏，您可以使用Windows中的几个工具。同样，它们远不完美，通常只能从外部调查正在运行的应用程序，而不是简单地在应用程序结束时报告泄漏。查找“微软调试工具”(UMDH，LeakDiag，gflag)。就我个人而言，我发现只需编写自己的内存管理器，并让它在应用程序结束时报告泄漏，就会容易得多。这并不难写。你要做的是：|67005|67006|实现了正确的new和delete运算符(我认为你应该实现4个new和4个delete作为new的实现)，获取调用堆栈(查找StackWalk)并将其与分配的内存一起存储。|67007|在构造函数中创建一个启动内存管理器的类，并将destructor.|67008|Make中的所有泄漏(包括调用堆栈)报告为该类类型的全局变量。可能需要使用#pragma(init_seg).|67009|将其设置为特殊的全局变量|67010|entityMap|0|LINK|mutability|MUTABLE|url|http://www.codersnotes.com/sleepy|1|http://lukestackwalker.sourceforge.net/^0|0|0|0|0|0|0|0|2J|X|0|41|13|1|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1B|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|1C|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|1D|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|1E|8|@]|9|@]|A|$]]|$1|H|3|I|5|E|7|1F|8|@]|9|@]|A|$]]|$1|J|3|K|5|E|7|1G|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|1H|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|1I|8|@]|9|@$O|1J|P|1K|1|1L]|$O|1M|P|1N|1|1O]]|A|$]]|$1|Q|3|R|5|6|7|1P|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|1Q|8|@]|9|@]|A|$]]|$1|T|3|U|5|E|7|1R|8|@]|9|@]|A|$]]|$1|V|3|W|5|E|7|1S|8|@]|9|@]|A|$]]|$1|X|3|Y|5|E|7|1T|8|@]|9|@]|A|$]]|$1|Z|3|10|5|6|7|1U|8|@]|9|@]|A|$]]|$1|11|3|-4|5|6|7|1V|8|@]|9|@]|A|$]]]|12|$13|$5|14|15|16|A|$17|18]]|19|$5|14|15|16|A|$17|1A]]]]

I used several commercial alternatives and although they can deliver fantastic results, they also often simply fail to work because of unknown reasons:

<ul>
<li>Rational Quantity: fantastic product for performance profiling, but they failed to release new versions during several years, and often (in my case) the software often refused to work</li>
<li>AQTime: also very good (less than Rational Quantity) but also sometimes refuses to work for unknown reasons.</li>
<li>Performance validator: same</li>
</ul>

In the last years I returned to the rather crude way of sampling the application. This is not as perfect as using instrumentation, but it's much faster, can be run on any application and always works. My favorite is "Very Sleepy" (<a href="http://www.codersnotes.com/sleepy" rel="nofollow noreferrer">http://www.codersnotes.com/sleepy</a>) but also Luke StackWalker (<a href="http://lukestackwalker.sourceforge.net/" rel="nofollow noreferrer">http://lukestackwalker.sourceforge.net/</a>) is quite good. Because the applications can be run immediately and without a noticeable slowdown, the "change app, profile" loop is very short and efficient.

For finding memory leaks, there are several tools in Windows that you can use. Again, they are far from perfect, and often can only investigate running applications from the outside, not simply reporting leaks at the end of the application. Look for the "Microsoft Debugging Tools" (UMDH, LeakDiag, gflags). Personally, I find it much easier just to write my own memory manager, and let it report the leaks at the end of the application. It's not that hard to write. What you have to do is:

<ul>
<li>Implement the correct new and delete operators (I think you should implement 4 new and 4 delete operators)</li>
<li>In the implementation of new, get the call stack (look for StackWalk) and store this with the allocated memory.</li>
<li>Make a class that starts your memory manager in the constructor, and report all the leaks (including the call stack) in the destructor.</li>
<li>Make a global variable of that class-type. It might be needed to make it a special global variable using a #pragma(init_seg).</li>
</ul>

blocks|key|67900|text|这里也有非常简单易用的泄漏检测代码：http://www.codeproject.com/kb/cpp/MemLeakDetect.aspx|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|67901|entityMap|0|LINK|mutability|MUTABLE|url|http://www.codeproject.com/kb/cpp/MemLeakDetect.aspx^0|I|1G|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

There's really simple and easy to use Leak Detection code here too: <a href="http://www.codeproject.com/kb/cpp/MemLeakDetect.aspx" rel="nofollow noreferrer">http://www.codeproject.com/kb/cpp/MemLeakDetect.aspx</a>

blocks|key|1979645|text|不确定如何链接到这个，我之前在回答类似的问题时发布了这个链接：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1979646|您可以使用umdh.exe捕获和比较泄漏发生之前和之后的进程快照。这在Debug二进制文件中工作得最好，但在Release中是可行的，只要符号路径被正确设置-它将给你在第一个和第二个快照之间分配的内存的callstack。|1979647|http://support.microsoft.com/kb/268343|offset|length|1979648|这种方法的优点是免费。|1979649|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|0|12|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|S|8|@]|9|@$F|T|G|U|1|V]]|A|$]]|$1|H|3|I|5|6|7|W|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|X|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|E]]]]

Not sure how to link to this, which I previously posted in response to a similar question:

You can use umdh.exe to capture and compare snapshots of the process before and after leak happens. This works best with Debug binaries but is viable with Release provided symbol paths are correctly set - it will give you the callstacks of memory allocated between the 1st and the 2nd snapshot.

<a href="http://support.microsoft.com/kb/268343" rel="nofollow noreferrer">http://support.microsoft.com/kb/268343</a>

This approach has the advantage of being free.

Anyone know of a profiler and leak detector that will work with VS2010 code? Preferably one that runs on Win7.

I've searched here and in google. I've found one leak detector that works (Memory Validator) but I'm not too impressed. For one thing it shows a bunch of menu leaks and stuff which I'm fairly confident are not real. I also tried GlowCode but it's JUST a profiler and refuses to install on win7.

I used to use AQtime. It had everything I needed, memory/resource leak detection, profiling various things, static analysis, etc. Unfortunately it gives bogus results now.

My main immediate issue is that VS2010 is saying there are leaks in a program that had none in VS2005. I'm almost certain it's false positives but I can't seem to find a good tool to verify this. Memory Validator doesn't show the same ones and the reporting of leaks from VS doesn't seem rational.

VS2010 profiler/leak detection

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

有没有人知道可以处理VS2010代码的分析器和检漏器？最好是在Win7上运行的。我已经在这里和谷歌上搜索过了。我已经找到了一个可以工作的泄漏检测器(内存验证器)，但我对此并不太感兴趣。一方面，它显示了一堆菜单泄漏和一些我相当确信不是真的东西。我也尝试过GlowCode，但它只是一个分析器，拒绝在win7上安装。我曾经使用过AQtime。它有我需要的一切，内存/资源泄漏检测，分析各种东西，静态分析，

问VS2010分析器/泄漏检测
EN

回答 6

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问VS2010分析器/泄漏检测EN

回答 6

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问VS2010分析器/泄漏检测
EN