blocks|key|1760058|text|我在过去使用过Boehm+collector，并取得了很好的效果。它是开源的，可以在商业软件中使用。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1760059|它是一个保守的收集器，由垃圾收集技术的最重要的研究人员之一开发了很长的历史。|1760060|entityMap|0|LINK|mutability|MUTABLE|url|http://hboehm.info/gc/^0|7|F|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]]|C|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]]]

I have used the <a href="http://hboehm.info/gc/" rel="noreferrer">Boehm collector</a> in the past with good success. It's open source and can be used in commercial software.

It's a conservative collector, and has a long history of development by one of the foremost researchers in garbage collection technology.

blocks|key|1760110|text|Boost有很大范围的smart+pointers，这意味着引用计数或删除范围退出或介入式引用计数。这些已经证明足以满足我们的需求。一个很大的优点是它是完全免费的，开源的，模板化的C%2B%2B。因为它是引用计数，所以在大多数情况下，当一个对象被销毁时，它是高度确定的。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1760111|entityMap|0|LINK|mutability|MUTABLE|url|http://www.boost.org/doc/libs/1_36_0/libs/smart_ptr/smart_ptr.htm^0|B|E|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]]]]

Boost has a great range of <a href="http://www.boost.org/doc/libs/1_36_0/libs/smart_ptr/smart_ptr.htm" rel="noreferrer">smart pointers</a> which impliment reference counting or delete-on-scope exit or intrusive reference counting. These have proven enough for our needs. A big plus is that it is all free, open source, templated C++. because it is reference counting, in most cases it is highly deterministic when an object gets destroyed.

blocks|key|1760018|text|The+Boehm+garbage+collector是免费提供的，而且应该相当不错(我自己没有第一手经验)|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1760019|有关C%2B%2B0x+proposal+for+the+Boehm+garbage+collector的理论论文|1760020|它最初被认为是让C%2B%2B0x+,+but+will+not+make+it+after+all+(由于时间限制，我想)。|1760021|Proprosal+N2670+(对垃圾收集器的最小支持)确实在2008年6月获得了批准，所以随着编译器实现的增加，以及标准的最终确定，C%2B%2B的垃圾收集世界肯定会改变……|1760022|entityMap|0|LINK|mutability|MUTABLE|url|https://hboehm.info/gc/|1|http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2007/n2310.pdf|2|http://herbsutter.spaces.live.com/Blog/cns!2D4327CC297151BB!330.entry|3|http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2008/n2670.htm^0|0|R|0|0|2|1A|1|0|E|W|2|0|0|F|3|0^^$0|@$1|2|3|4|5|6|7|X|8|@]|9|@$A|Y|B|Z|1|10]]|C|$]]|$1|D|3|E|5|6|7|11|8|@]|9|@$A|12|B|13|1|14]]|C|$]]|$1|F|3|G|5|6|7|15|8|@]|9|@$A|16|B|17|1|18]]|C|$]]|$1|H|3|I|5|6|7|19|8|@]|9|@$A|1A|B|1B|1|1C]]|C|$]]|$1|J|3|-4|5|6|7|1D|8|@]|9|@]|C|$]]]|K|$L|$5|M|N|O|C|$P|Q]]|R|$5|M|N|O|C|$P|S]]|T|$5|M|N|O|C|$P|U]]|V|$5|M|N|O|C|$P|W]]]]

<a href="https://hboehm.info/gc/" rel="nofollow noreferrer">The Boehm garbage collector</a> is freely available, and supposedly rather good (no first hand experience myself)
Theoretical paper (in PDF) about <a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2007/n2310.pdf" rel="nofollow noreferrer">C++0x proposal for the Boehm garbage collector</a>
It was originally said to make C++0x <a href="http://herbsutter.spaces.live.com/Blog/cns!2D4327CC297151BB!330.entry" rel="nofollow noreferrer">, but will not make it after all</a> (due to time constraints I suppose).
<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2008/n2670.htm" rel="nofollow noreferrer">Proprosal N2670</a> (minimal support for garbage collectors) did get approved in june 2008 though, so as compiler implementations pick up on this, and the standard gets finalised, the garbage collection world out there for C++ is sure to change...

blocks|key|1760268|text|我经常使用boehm+gc。它使用起来很简单，但是文档实在太差了。有一个C%2B%2B页面，但是很难找到。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1760269|基本上，您只需确保每个类都继承它们的基类，并且始终将gc_allocator传递给容器。在许多情况下，您希望使用libgccpp来捕获new和delete的其他用法。这些在很大程度上是高级更改，我们发现可以在编译时使用#ifdef关闭GC，支持这一点只会影响一两个文件。|1760270|我的主要问题是你不能再使用Valgrind了，除非你先关闭收集器。虽然关闭收集器很容易，而且不需要重新编译，但如果内存开始耗尽，显然不可能使用它。|1760271|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|$]]

I use boehm-gc a lot. It is straight-forward to use, but the documentation is really poor. There is a C++ page, but its quite hard to find.

Basically, you just make sure that every class inherits from their base class, and that you always pass gc_allocator to a container. In a number of cases you want to use libgccpp to catch other uses of new and delete. These are largely high-level changes, and we find that we can turn off the GC at compile-time using an #ifdef, and that supporting this only affects one or two files.

My major problem with it is that you can no longer use Valgrind, unless you turn the collector off first. While turning the collector off is easy to do, and doesn't require recompiling, it's obviously impossible to use it if you start to run out of memory.

blocks|key|1545199|text|我唯一知道的是Boehm，它的底部是一个传统的标记和清扫。它可能使用各种技术来优化这一点，但通常情况下，如果没有像.Net+C%2B%2B这样的托管子集，就很难为C%2B%2B创建增量/分代/压缩GC。一些需要移动指针的方法可以使用编译器对固定指针或读/写块的支持来实现，但对性能的影响可能太大，而且对GC的更改不一定是微不足道的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1545200|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|$]]

The only one I know of is Boehm, which at the bottom is a traditional mark and sweep. It probably uses various techniques to optimize this, but typically incremental/generational/compacting GC's will be hard to create for C++ without going for a managed subset such as what you can get with .Net C++. Some of the approaches that needs to move pointers can be implemented with compiler support for pinning pointers or read/write blocks though, but the effect on performance may be too big, and it isn't necessarily non-trivial changes to the GC.

blocks|key|1760132|text|在C%2B%2B中，GC的主要困难在于需要处理GC意义上的不协作模块。也就是说，处理那些从来没有考虑过GC的库。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1760133|这就是为什么经常建议使用Boehm。|1760134|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

The major difficulty with GC's in C++ is the need to handle uncooperative modules, in the GC sense. ie, to deal with libraries that were never written with GC's in mind.

This is why the Boehm GC is often suggested.

blocks|key|1760172|text|这是我在寻找同样的东西时发现的一个商业产品|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1760173|HnxGC+http://hnxgc.harnixworld.com/|offset|length|1760174|当时，测地系统公司也有一款名为Great+Circle的产品，但现在看起来他们不再卖了。不知道他们有没有把产品卖给别人。|1760175|entityMap|0|LINK|mutability|MUTABLE|url|http://hnxgc.harnixworld.com/^0|0|6|T|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@$D|R|E|S|1|T]]|A|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]]]

Here's a commercial product I found in just looking for this same thing

HnxGC <a href="http://hnxgc.harnixworld.com/" rel="nofollow noreferrer">http://hnxgc.harnixworld.com/</a>

Back in the day, there was also a product called Great Circle from Geodesic Systems, but doesn't look like they sell that anymore. No idea if the sold the product to anyone else.

blocks|key|1760198|text|你也可以使用微软的托管C%2B%2B。CLR和GC非常可靠，并在服务器产品中使用，但您必须使用CLR类型才能让GC实际收集-您不能仅重新编译现有代码并删除所有delete语句。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1760199|我宁愿使用C#来编写全新的代码，但是托管C%2B%2B可以让您以更渐进的方式发展您的代码库。|1760200|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

You can also use Microsoft's Managed C++. The CLR and the GC are very solid and used in server products, but you have to use CLR types for the GC to actually collect - you can't just recompile your existing code and remove all the delete statements.

I would rather use C# to write brand new code, but Managed C++ lets you evolve your code base in a more progressive manner.

What free and commercial garbage collection libraries are available for C++, and what are the pros and cons of each?

I am interested in hard-won lessons from actual use in the field, not marketing or promotional blurb.

There is no need to elaborate on the usual trade offs associated with automatic garbage collection, but please do mention the algorithms used (reference counting, mark and sweep, incremental, etc.) and briefly summarise the consequences.

Garbage collection Libraries in C++

服务器

编译器

容器

有哪些免费的和商业的垃圾回收库可供C++使用，每个库的优缺点是什么？我感兴趣的是来自该领域实际应用的来之不易的经验教训，而不是营销或推广简介。没有必要详细说明与自动垃圾收集相关的常见权衡，但请一定要提到所使用的算法(引用计数、标记和清除、增量等)。并简要总结其后果。

问C++中的垃圾回收库
EN

回答 8

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问C++中的垃圾回收库EN

回答 8

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问C++中的垃圾回收库
EN