blocks|key|2063350|text|对于静态数组，如果创建了数组的内容，只需释放所创建的对象即可。您不需要做任何特殊的事情来清理myArr本身使用的空间。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2063351|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|$]]

Regarding static arrays, if you created the contents of the array, just free those objects you created. You don't need to do anything special to clean up the space used by myArr itself.

blocks|key|984317|text|COM对象是通过接口引用的，您不需要做任何空闲的操作。编译器负责必要的引用计数逻辑，以确保在正确的时间处理COM对象。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|984318|至于静态数组(或者说动态数组)，您也不需要释放它们。如果它们包含对象，那么必须在适当的时候释放对象，但是数组不能释放。|984319|此外，不要在任何不是对象引用的东西上使用FreeAndNil。与接口或其他变量一起使用它会破坏内存。最好不要使用它(用免费代替)，除非您正在处理一个需要释放的对象，然后再进行重用。|984320|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|$]]

COM objects are referenced via Interfaces, which you don't need to do anything to free. The compiler takes care of the necessary reference-counting logic to make sure the COM object will be disposed of at the right time.

As for static arrays, (or dynamic arrays, for that matter,) they don't need to be freed by you either. If they contain objects then the objects have to be freed at the appropriate time, but the arrays don't.

Also, never use FreeAndNil on anything that's not an object reference. Using it with interfaces or other variables can corrupt memory. It's best to never use it (use Free instead) unless you're dealing with an object that you need to free and then reuse later.

blocks|key|984327|text|首先，在大多数情况下，FreeAndNil有点过火。当您将对象的字段释放在析构函数或全局(丑陋)变量上时，它非常方便。但大多数时候，只打免费电话就足够了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|984328|您应该知道，对象变量实际上是指向对象数据的指针。当您调用Free时，该缓冲区将被释放(当然，在运行析构函数之后)，但是对象变量仍然指向刚刚释放的内存位置。它被称为“悬空指针”。有一个悬空指针并不是一个问题，只要你知道它在这个上下文中悬挂。例如：|984329|Procedure+Myproc;
var+vString+:+TStringList;
begin
++//Here,+vString+is+"dangling"
++vString+:=+TStringList.Create;
++//Here,+vString+is+valid
++try
++++//Do+some+stuff
++finally
++++vString.Free;
++end;
++//Here,+vString+is+"dangling"...++But+who+care,+it's+about+to+go+out+of+scope+and+we+won't+use+it+again.
end;|code-block|syntax|javascript|984330|在不知道何时或如何释放变量的全局变量上调用FreeAndNil更有意义。尽管如此，一直调用FreeAndNil并没有什么错(除了在非常紧的循环中，您试图获得性能的每一个oz+)。|984331|现在，对于COM对象..。就像梅森所说的，它们是参考计算的。因此，如果您持有对该接口的唯一引用，调用MyInterface+:=+nil;将释放它。但是，当/如果变量超出作用域时，编译器将负责添加清理代码，以确保接口引用减少。因此，如果您试图将内存需求保持在最低限度，请将接口设置为零。否则，就没那么重要了。|offset|length|style|CODE|984332|至于你的排列..。你可以在名单上的每一件物品上打电话.在那之后，选择将他们设为零。|984333|entityMap^0|0|0|0|0|1E|J|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|W|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|X|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|Y|8|@$M|Z|N|10|O|P]]|9|@]|A|$]]|$1|Q|3|R|5|6|7|11|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|T|$]]

First, in most situation, FreeAndNil is a bit of overkill. It's handy when you free and object's field outside it's destructor, or on a global(ugly) variable. But most of the time, just calling free is enough.

As you should know, an object variable is actually a pointer to the object's data. When you call Free, that buffer is freed (after the destructor is ran, of course), but the Object variable still points to the memory position that was just freed. It's called a "Dangling pointer". Having a dangling pointer is not a problem as long as you KNOW it's dangling in that context. For exemple:

<pre><code>Procedure Myproc;
var vString : TStringList;
begin
 //Here, vString is "dangling"
 vString := TStringList.Create;
 //Here, vString is valid
 try
 //Do some stuff
 finally
 vString.Free;
 end;
 //Here, vString is "dangling"... But who care, it's about to go out of scope and we won't use it again.
end;
</code></pre>

Calling FreeAndNil makes more sense on global variable where you don't know exactly when or how the variable can be freed. With that being said, there is nothing wrong in calling FreeAndNil all the time (except in very tight loops where you try to get every oz of performance).

Now, for the COM objects... Like Mason stated, they are reference counted. So if you hold the only reference to that interface, calling <code>MyInterface := nil;</code> will free it. But when/if the variable goes out of scope, the compiler take care of adding cleanup code to make sure the interface reference is decremented. So if you are trying to keep the memory requirement to a minimum, set the interface to nil. Otherwise, it doesn't matter that much.

As for your array... You can just call Free on every items in the list... Optionnaly set them to nil after.

I haven't been able to find the answers to a couple of my Delphi memory management questions. I could test different scenarios (which I did to find out what breaks the FreeAndNil method), but its takes too long and its hard! But seriously, I would also like to know how you all (Delphi developers) handle these memory management issues.

My Questions (Feel free to pose your own I'm sure the answers to them will help me too):

<ol>
<li>Does FreeAndNil work for COM objects? My thoughts are I don't need it, but if all I need to do is set it to nil than why not stay consistent in my finally block and use FreeAndNil for everything?</li>
<li>Whats the proper way to clean up static arrays (myArr : Array[0..5] of TObject). I can't FreeAndNil it, so is it good enough to just set it to nil (do I need to do that after I've FreeAnNil'd each object?)?</li>
</ol>

Thanks Guys!

Delphi Memory Management

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

我还没有找到一些我的Delphi内存管理问题的答案。我可以测试不同的场景(为了找出破坏FreeAndNil方法的原因而做的)，但是它花费的时间太长，而且很难！但是说真的，我也想知道你们(Delphi开发人员)是如何处理这些内存管理问题的。我的问题(请随意提出你自己的问题，我相信答案也会对我有所帮助)：为COM对象工作F...

问Delphi内存管理
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Delphi内存管理EN