Eclipse的崩溃有超过GC开销极限误差 [英] Eclipse crashes with a GC overhead limit exceeded error

问题描述

这是我第一次使用Proguard的，我已经注意到，如果你添加许多自定义规则 ProGuard的-project.txt 这显然需要更多的时间用于建设。这是导致Eclipse的崩溃报告超过了 GC开销限制，然后我必须强制关闭的Java下来，因为编辑器继续弹出错误和警告对话框。有什么办法避免对Eclipse的这些连续死机等修复报告的问题<一href="http://stackoverflow.com/questions/1393486/error-java-lang-outofmemoryerror-gc-overhead-limit-exceeded">here呢？

It's the first time I am using Proguard, I've noticed that if you add many custom rules to proguard-project.txt it takes obviously much more time for building. That's cause Eclipse to crash reporting a GC overhead limit exceeded and then I have to force the shut down of java because the editor continues to pop out error and alert dialogs. Is there any way to avoid these continuous crashes on Eclipse and so fix the problem reported here too?

推荐答案

固定的，我了解这个问题的所有其他论坛的帖子，但没有人说如何解决它在Eclipse上。我发现这里修复

Fixed, I read all the others forum posts about the problem but no one said how to fix it on Eclipse. I found the fix here

编辑：万一链路变为死了，这里是你可以做什么。编辑的eclipse.ini，并设置这样的事情：

in case the link becomes dead, here's what you can do. Edit "eclipse.ini", and set something like that:

-XX:MaxPermSize=1024m
-Xms512m
-Xmx1024m

这篇关于Eclipse的崩溃有超过GC开销极限误差的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！