blocks|key|2344118|text|不，只有内存泄漏，内存是由FastMM分配的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2344119|编辑：，也许答案看起来是包装的，但它不是！如果有人检查+FastMM++haw，会发现内存定位的每个指针都被推入其中一个堆栈(并且弹出在FreeMem)中(有更多的堆栈，取决于内存大小)，因此在关闭应用程序结束时，FastMM只检查堆栈，如果堆栈中有东西，如果是，则报告内存泄漏！|offset|length|style|BOLD|2344120|entityMap^0|0|0|3|R|8|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@$D|L|E|M|F|G]|$D|N|E|O|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|P|8|@]|9|@]|A|$]]]|I|$]]

No, only memory leaks which memory was alocated by FastMM.

EDIT:
Maybe the answer looks wrapped but it is not! If anyone check the FastMM haw is made than can see that every pointer of memory alocation is pushed (and poped out at FreeMem) in to one of stacks (there is more stacks, depend of memory size) so at the end of closing application the FastMM only check stacks, if something in stacks, and if it is, than report memory leak!

blocks|key|2344094|text|FastMM是Windows内存管理之上的一个层。显然，如果您(或某个组件或其他组件)使用Windows分配内存，那么这种分配将绕过FastMM，您将无法跟踪它。顺便说一句，Delphi内存管理器自己使用API来分配内存块。因此，如果您需要看到在这个级别上的分配，FastMM是不够的-您必须使用像AQTime和类似的工具(正如我在前面的问题中所建议的)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2344095|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

FastMM is a layer on top of Windows memory management. Obviously, if you (or some component or whatever) uses Windows APIs to allocate memory, then such allocation bypasses FastMM and you won't be able to track it. BTW Delphi memory managers themselves use that APIs to allocate chunks of memory. So if you need to see allocations on that level, FastMM is not enough - you must use tools like AQTime and similar (as I suggested in the previous question).

blocks|key|788920|text|我从来不知道FastMM无法检测到内存泄漏。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|788921|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I've never known FastMM to fail to detect a memory leak.

blocks|key|789060|text|有几种可能的原因：(适用于任何内存管理器)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|789061|您的主程序循环会泄漏内存，但会泄漏到在关闭时释放的内容。|unordered-list-item|789062|最简单的情况是记录备忘录。备忘录越来越大，但一旦关闭，备忘录就被销毁了。|789063|789064|​|789065|内存被分配到fastmm控制的之外|789066|直接从窗口分配|789067|分配给dll等的内存。|789068|789069|789070|堆碎片。内存管理器保持分配的大块(例如，因为它仍然包含分配的一小部分)。结果:该应用程序不使用它，但它也没有发布到操作系统。运行时/内存管理器将其保存在周围。|789071|fastmm应该能更好地抵御这种现象，但是毫无疑问，请尝试打印堆管理器信息，看看是否是这样。|789072|789073|789074|entityMap^0|0|1|1|0|0|1|1|1|0|0|1|1|0|0^^$0|@$1|2|3|4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|10|8|@]|9|@]|A|$]]|$1|E|3|F|5|D|7|11|8|@]|9|@]|A|$]]|$1|G|3|-4|5|6|7|12|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|13|8|@]|9|@]|A|$]]|$1|J|3|K|5|D|7|14|8|@]|9|@]|A|$]]|$1|L|3|M|5|D|7|15|8|@]|9|@]|A|$]]|$1|N|3|O|5|D|7|16|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|17|8|@]|9|@]|A|$]]|$1|Q|3|I|5|6|7|18|8|@]|9|@]|A|$]]|$1|R|3|S|5|D|7|19|8|@]|9|@]|A|$]]|$1|T|3|U|5|D|7|1A|8|@]|9|@]|A|$]]|$1|V|3|-4|5|6|7|1B|8|@]|9|@]|A|$]]|$1|W|3|I|5|6|7|1C|8|@]|9|@]|A|$]]|$1|X|3|-4|5|6|7|1D|8|@]|9|@]|A|$]]]|Y|$]]

There are several possible causes: (which apply to any memory manager)

<ul>
<li>your main program loop leaks memory, but does so to something that is freed on shutdown
<ul>
<li>the simplest case is logging to a memo. The memo gets bigger and bigger, but is destroyed on shutdown.</li>
</ul></li>
<li>the memory is allocated outside fastmm's control
<ul>
<li>directly allocating from windows</li>
<li>memory allocated in dlls etc.</li>
</ul></li>
<li>Heapfragmentation. A memory manager keeps large blocks allocated (e.g. because it still contains a small % of allocations). Result: The app doesn't use it, but it is not release to the OS either. The runtime/memorymanager keeps it around.
<ul>
<li>fastmm should be more resilient against this phenomena, but in doubt try to print heapmanager info to see if this is the case.</li>
</ul></li>
</ul>

blocks|key|2344168|text|FastMM不会检测没有通过FastMM的内存分配的泄漏。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2344169|这可以包括您使用的第三方库或DLL的GlobalAlloc调用。|2344170|编辑：微软的MSDN有一个很好的内存分配方法列表。|offset|length|style|BOLD|2344171|事实上，这就是我在我的回答中提到的以前FastMM问题中提到的问题。|2344172|您可以使用像VMMap这样的工具来跟踪FastMM无法检测到的内存泄漏。|2344173|-耶伦|2344174|entityMap|0|LINK|mutability|MUTABLE|url|http://msdn.microsoft.com/en-us/library/aa366533(v=vs.85).aspx)|1|https://stackoverflow.com/questions/4463979/my-program-never-releases-the-memory-back-why/4464907#4464907|2|http://technet.microsoft.com/en-us/sysinternals/dd535533^0|0|0|0|2|D|B|0|0|9|4|1|0|6|5|2|0|0^^$0|@$1|2|3|4|5|6|7|11|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|12|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|13|8|@$F|14|G|15|H|I]]|9|@$F|16|G|17|1|18]]|A|$]]|$1|J|3|K|5|6|7|19|8|@]|9|@$F|1A|G|1B|1|1C]]|A|$]]|$1|L|3|M|5|6|7|1D|8|@]|9|@$F|1E|G|1F|1|1G]]|A|$]]|$1|N|3|O|5|6|7|1H|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|1I|8|@]|9|@]|A|$]]]|Q|$R|$5|S|T|U|A|$V|W]]|X|$5|S|T|U|A|$V|Y]]|Z|$5|S|T|U|A|$V|10]]]]

FastMM does not detect leaks of memory allocations not going through FastMM.

This can include GlobalAlloc calls from 3rd party libraries or DLLs you use. 
Edit: Microsoft's MSDN has a <a href="http://msdn.microsoft.com/en-us/library/aa366533(v=vs.85).aspx" rel="nofollow noreferrer">nice list of memory allocation methods</a>.

This was in fact the problem I mentioned I mentioned in <a href="https://stackoverflow.com/questions/4463979/my-program-never-releases-the-memory-back-why/4464907#4464907">my answer</a> to your previous FastMM question.

You can use a tool like <a href="http://technet.microsoft.com/en-us/sysinternals/dd535533" rel="nofollow noreferrer">VMMap</a> to track the memory leaks that FastMM cannot detect.

--jeroen

blocks|key|2344182|text|已经有很多很好的答案了，但有一点还没提出来.|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2344183|由于内存已被释放，许多“泄漏”将不会被大多数内存泄漏检测器检测到，但在它不再被使用之后的很长一段时间内。例如，将对象堆在TObjectList中。对象放在对象列表中，但是在使用完它们之后，就不会释放它们。当对象列表也被销毁时，它们也将被销毁(当应用程序关闭时，假设是OwnsObject=True)。由于对象实际上是被释放的，所以对象不会被“泄漏”，但随着时间的推移，仍然会使应用程序使用越来越多的内存。|2344184|FastMM不会报告这些，因为它只进行“全面运行”分析。要检测这些，您需要一个允许部分运行的内存泄漏检测器，也就是说，在执行过程中分析A点和B点之间的“泄漏”。尤金提到的AQTime允许这种检查。但是请注意，is需要进行一些分析，因为这将产生许多假阳性(几乎所有的"realloc“操作都会被标记为泄漏)。|2344185|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

There is a lot of good answer already, but one point that wasn't mentionned yet...

There is a lot of "leaks" that won't get detected by most memory leak detector since the memory IS freed, but way after it isn't used anymore. For exemple, object stacked in a TObjectList. Object are put in the object list, but after you are done using them, you don't free them. They will be destroyed when the object list is destroyed too (When application close for exemple, assuming OwnsObject=True). Since the objects are actually freed, objects are not "leaked", but still make your application use more and more memory over time.

FastMM won't report those as it only makes "full run" analysis. To detect those, you need a memory leak detector that allows to do partial runs, that is, analyzing what "leaked" between point A and point B during the execution. AQTime that Eugene mentionned allow that kind of checks. But be aware that is takes a bit of analysis because that will yield many false-positive (Pretty much all "realloc" operations will be marked as a leak).

Somebody suggested recently ( <a href="https://stackoverflow.com/questions/4463979/my-program-never-releases-the-memory-back-why">My program never releases the memory back. Why?</a> ) that my program leaks some memory. I have FastMM set to aggressive and it reports no memory leaks when I shutdown the program. 

Anyway, I would like to know if there can be memory leaks that are no detected by FastMM? 

Update: I don't personally use Win API to allocate memory. But I am afraid that some 3rd party components I use (not so many) may use it. Can you let me know all possible API calls that FastMM cannot intercept? I will do a search in my code for them. Thanks.

<hr>

Delphi 7, Win 7 32 bit 
FastMM 4.97 
I am not interested about interfaces.

Does FastMM detect all memory leaks

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

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

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

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

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

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

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

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

最近有人(  )建议我的程序泄漏一些内存。我已经将FastMM设置为积极的，当我关闭程序时，它没有报告内存泄漏。不管怎样，我想知道是否会有FastMM没有检测到的内存泄漏？更新:我个人不使用Win API来分配内存。但我担心我使用的一些第三方组件(不是很多)可能会使用它。你能告诉我所有FastMM无法拦截的可能的API调用吗？我会在我的代码中搜索他们。谢谢。德尔菲7，赢7 32位FastMM 4.

问FastMM是否检测到所有内存泄漏
EN

回答 6

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问FastMM是否检测到所有内存泄漏EN

回答 6

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问FastMM是否检测到所有内存泄漏
EN