blocks|key|1956560|text|您在这里混合了抽象级别:内存泄漏是由于库中的错误(在库中，对象之间相互引用，'a持有引用b‘)，以及在实现垃圾收集器的效率和准确性之间的权衡。你想花多少时间来找出这样的循环？如果你花了两倍的钱，你就能检测到两倍长的循环。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1956561|因此，内存泄漏问题并不是编程语言特有的问题，没有理由让GO本身比Java更好或更糟。|1956562|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 are mixing abstraction levels here: the memory leaks are due to bugs in the library (where objects reference each other though chains of 'a holds reference to b' as well as a trade-off in the implementation of the garbage collector between efficiency and accuracy. How much time do you want to spend on finding out such loops? If you spend twice as much, you'll be able to detect loops twice as long.

So the memory leak issue is not programming language specific, there is no reason that by itself GO should be better or worse than Java.

blocks|key|758899|text|不管是否垃圾收集，您都可以编写一个内存泄漏的程序--+Java、Go或任何其他语言的泄漏。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|758900|垃圾收集确实减轻了程序员的一些负担，但它并不能完全防止泄漏。|758901|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|$]]

Garbage collection or not, you can write a program that has memory-leaks in Java, Go, or any other language for the most part.

Garbage Collection does take some of the burden off the programmer but it does not prevent leaks entirely.

blocks|key|1956639|text|Go程序很可能会出现内存泄漏。Go的当前实现有一个简单的标记和扫描垃圾收集器。这只是作为一个临时解决方案，而不是作为长期垃圾收集器。有关更多信息，请参见此页面。在标题Go+Garbage+Collector下面查看。如果您愿意的话，该页面甚至有一个指向当前版本代码的链接。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1956640|entityMap|0|LINK|mutability|MUTABLE|url|http://code.google.com/p/try-catch-finally/wiki/GoInternals^0|2B|K|25|2|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@$9|O|A|P|B|C]]|D|@$9|Q|A|R|1|S]]|E|$]]|$1|F|3|-4|5|6|7|T|8|@]|D|@]|E|$]]]|G|$H|$5|I|J|K|E|$L|M]]]]

It's very possible that Go programs will exhibit memory leaks. The current implementation of Go has a simple mark-and-sweep garbage collector. This is only intended as a temporary solution and is not intended as the long term garbage collector. See this <a href="http://code.google.com/p/try-catch-finally/wiki/GoInternals" rel="noreferrer">page</a> for more info. Look under the header <code>Go Garbage Collector</code>. That page even has a link to code for the current version if you are so inclined.

blocks|key|1956667|text|“内存泄漏”是指程序员认为会释放的一段内存没有被释放。这种情况可以发生在任何语言中，垃圾收集或不收集。在GC语言中，通常的原因是保留对内存的额外引用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1956668|“语言不会导致内存泄漏，程序员会导致内存泄漏”。|1956669|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|$]]

A 'memory leak' is when a piece of memory that the programmer thought would be freed isn't freed. This can happen in any language, garbage collected or not. The usual cause in GC languages is retaining an additional reference to the memory.

"Languages don't cause memory leaks, programmers cause memory leaks".

blocks|key|2313682|text|您在这里混淆了不同类型的内存泄漏。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2313683|基于内存管理的令人发指的、显式的内存泄漏以Java+(或任何其他基于GC的语言)消失了。这些泄漏是由于完全失去对内存块的访问而不将它们标记为未使用造成的。|2313684|“内存泄漏”仍然存在于Java和地球表面的每一种语言中，直到计算机能够读取我们的思想，并将在可预见的将来。这些泄漏是由代码/程序员保持对技术上不再需要的对象的引用造成的。这些基本上都是逻辑错误，在任何使用现有技术的语言中都无法防止。|2313685|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|$]]

You are confusing different types of memory leaks here. 

The heinous, explicit-memory-management based memory leaks are gone in Java (or any other GC based language). These leaks are caused by completely losing access to chunks of memory without marking them as unused.

The "memory leaks" still present in Java and every other language on the face of the planet until the computer can read our minds are still with us, and will be for the foreseeable future. These leaks are caused by the code/programmer keeping references to objects which are technically no longer needed. These are fundamentally logic bugs, and cannot be prevented in any language using current technologies.

Here are the facts:

<ul>
<li>the language Go has a garbage collector. </li>
<li>Java has a garbage collection</li>
<li>a lot of Java programs have (subtle or not) memory leaks</li>
</ul>

As an example of a Java program that has memory leaks (not for the faint of heart, the question may shake your beliefs), see here about a little Java program called Tomcat that even has a "find leaks" button: <a href="https://stackoverflow.com/questions/4565105">Is there a way to avoid undeployment memory leaks in Tomcat?</a>

So I am wondering: will programs written in Go exhibit the same kind of (subtle or not) memory leaks that some programs written in Java exhibit?

Is Go subject to the same subtle memory-leaks that Java is?

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

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

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

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

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

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

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

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

社区新版编辑器体验调研

以下是事实：Go语言有一个垃圾收集器。Java有一个垃圾收集很多Java程序都有内存泄漏(不管是不是很微妙)作为一个Java程序的例子，它有内存泄漏(不是针对心脏无力的人，这个问题可能动摇你的信念)，在这里可以看到一个名为Tomcat的小型Java程序，它甚至有一个“查找泄漏”按钮：。因此，我想知道:用Go编写的程序是...

问会不会受到Java那样微妙的内存泄漏的影响呢？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问会不会受到Java那样微妙的内存泄漏的影响呢？EN